On Fri, 17 Jan 2003, Alexis Vartanian wrote: > Regarding: thread bug in xc/lib/GL/glx/glxcmd.c and glxext.c > Email: [EMAIL PROTECTED] > ------------------------------------------------------------ > XFree86 Version: XFree4.*.*
> OS: linux rh7.3 > Area: Xlib > Server: XFree86 (The XFree86 4.x server) > Description: > version : XFree 4.* > problem : GL application hangs at starting (quake3 and a threaded) > when running a multithread application, any call to _XRead should > be done after a XLockDisplay is called. If you don't do that, > a call to _XRead may make a call to _XWaitForReadable that calls > XUnlockDisplay then XLockDisplay then the application freezes in the > next XLockDisplay > this is not the case in : > glxext.c:387 and glxcmd.c:1439 > the correction should be fairly easy, moving the XUnlockDisplay done > earlier at the end of the function and anywhere in the path where > the function exits > I can provide a patch if wanted > Repeat By: > not easy at all, never seen before, depends execution order > but the glx code is obviously incorrect A fix for this has been committed. Thanks for reporting the problem. Marc. +----------------------------------+-----------------------------------+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax: 1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +-----------------------------------+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply | | CANADA | | +----------------------------------+-----------------------------------+ XFree86 Core Team member. ATI driver and X server internals. _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
