Michel D�nzer wrote:
[ please move this thread to the appropriate development list(s) ]

On Fre, 2003-01-17 at 16:03, Alexis Vartanian wrote:
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

Please do.


Michel, do you have a patch for this. I think this problem has come up in a separate instance with multithreaded applications -- it would be good to get it resolved.

Keith



-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to