On Sat, Feb 22, 2003 at 12:00:03PM -0700, Keith Whitwell wrote: > >3. A good old segfault: > >Program received signal SIGSEGV, Segmentation fault. > > This occurs because you have modified the X event loop to destroy a context > that *IS STILL IN USE* in another thread. GL doesn't provide any > guarantees about what will happen if you try to do this...
Whoops, I see that now. > One way to achieve something like what you want would be to make ExitFlag > an array, and destroy the context at the end of draw_loop. I've attached > something that does this. > > This doesn't solve all of your problems, though - I'm still looking at them. I was more concerned with the other two (drmCmdBuffer: -22 and the vtx assert error) in anycase, as I see them daily whilst using a VTK based application. Thanks very much for looking into this! Thanks, Charl -- charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
