Chris, Excellent detective work. It looks like longjmp setjmp is the way to go. I will give it a try someday, unless you want to do it first.
The reason that catching a server reset is so important is that we should not be killed when the server resets and we should try to connect to the server again if it resets. Part of this makes it easy to stay connected when a user is using XDMCP to connect to a remote machine. Also, we can never integrate clipboard support into XWin.exe until we can be assured that the server will not be killed when it resets. Later, Harold Chris Twiner wrote: > Harold, > > As an aside this link explains that the only way is to longjmp/setjmp. > > http://www.faqs.org/faqs/Xt-FAQ/section-19.html > > If the intention is to fully integrate xwinclip into XWin then this > would be unwanted to say the least. Given XWin would close anyway > you'd still want xwinclip to close with it. > > Chris > > _________________________________________________________________ > Join the world’s largest e-mail service with MSN Hotmail. > http://www.hotmail.com >