Add Comment
|
Related Links
|
TrackBack
Gracefully Handle XOpenDisplay ErrorsAll you say is crystal clear, thanks. In fact, I get into this error when calling the XOpenDisplay function from within an application running on a remote Unix machine (connected to using PuTTY with X forwarding enabled), when there is not any Xserver (e.g. XMing) running on the local machine. Of course this behavior is expected. My problem is that in this case my application is aborted, and I do not want this. I want to manage the error condition within the application. But it seems that checking the value returned by XOpenDisplay against NULL is not enough, because XOpenDisplay does not return at all ! Is there some setting I should change, some interrupt I should mask, or some harmless check I should do before calling XOpenDisplay ? Thanks. nomoreties
Add Comment
|
Related Links
|
TrackBack
Did your message disappear? Read the Forums FAQ. Add CommentSpam Control | * indicates required field TrackBackTrackBack only accepted from WebSite-X Suite web sites. Do not submit TrackBacks from other sites. Send Ping | TrackBack URL | Spam Control No TrackBacks yet. TrackBack can be used to link this thread to your weblog, or link your weblog to this thread. In addition, TrackBack can be used as a form of remote commenting. Rather than posting the comment directly on this thread, you can posts it on your own weblog. Then have your weblog sends a TrackBack ping to the TrackBack URL, so that your post would show up here. Messages, files, and images copyright by respective owners. |
Products
|
Services
48 Users Online
|
Copyright © 1996 - 2024. All Rights Reserved. |