Re: Seppuku and x_IO_error_handler()

Friday, 28 August 1998

        Pete Ware <ware(a)cis.ohio-state.edu&gt; writes:

...
 The only way around this is to use setjmp/longjmp to avoid returning
to the
 I/O error handler.  The following code fragment demonstrates this:

 #include <setjmp.h>
 jmp_buf XIOrecover;

 void
 XIOHandler (dpy)
         Display         *dpy;
 {
         destroyDisplay (dpy);
         longjmp (XIOrecover, 1);
 }

 main ()
 {
         ...
         if (setjmp (XIOrecover) == 0)
                 XSetIOErrorHandler (XIOHandler);
         XtAppMainLoop (app_context);
 } 

	Yes. This is exactly the kind of things I had in mind.

...
 There was much discussion in comp.windows.x about this topic in
 November of 91.  Robert Scheifler posted an article which basically
 said this is the way it will be and Xlib will not change. 
	Pffffff :-( Sounds like the time when you can write a clean
multi-threaded application managing several displays has not come yet...

-- 
    /     /   _   _       Didier Verna        http://www.inf.enst.fr/~verna/
 - / / - / / /_/ /      E.N.S.T. INF C201.1      mailto:verna＠inf.enst.fr
/_/ / /_/ / /__ /        46 rue Barrault        Tel.   (33) 01 45 81 80 72
                      75634 Paris  cedex 13     Fax.   (33) 01 45 81 31 19

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998