This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: Integrating xwinclip support
- From: Brian Genisio <briangenisio at yahoo dot com>
- To: Alexander Gottwald <Alexander dot Gottwald at informatik dot tu-chemnitz dot de>
- Cc: cygwin-xfree at cygwin dot com
- Date: Sun, 3 Feb 2002 08:50:56 -0800 (PST)
- Subject: Re: Integrating xwinclip support
> man XSetIOErrorHandler:
>
> The XSetIOErrorHandler sets the fatal I/O error handler.
> Xlib calls the program's supplied error handler if any
> sort of system call error occurs (for example, the connec
> tion to the server was lost). This is assumed to be a
> fatal condition, and the called routine should not return.
> If the I/O error handler does return, the client process
> exits.
>
> To avoid the return you might return via setjmp/longjmp back to the startup
> code (and maybe sleep a while before doing so)
>
I am not sure that would be the best programming practice... (I could be wrong)
Wont that leave the IOErrorHandler function call still on the stack, causing
problems on multiple restarts of the server?
Or does that setjmp/longjmp change the address of the return completely? Will
that leave other calls on the stack? If I am wrong on this, could you explain
this practice please? I have never used such a technique, and I am curious.
Brian
> HTH
> ago
> --
> Alexander.Gottwald@informatik.tu-chemnitz.de
> http://www.gotti.org ICQ: 126018723
> phone: +49 3725 349 80 80 mobile: +49 172 7854017
> 4. Chemnitzer Linux-Tag http://www.tu-chemnitz.de/linux/tag/lt4
>
__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions!
http://auctions.yahoo.com