Re: [Mesa3d-dev] Bug in mesa-master: Deadlock for multi-threaded glx apps inside __glXInitialize()

[Mario K. <mar...@tu...>]

On Aug 2, 2010, at 3:55 PM, Kristian Høgsberg wrote:
>
> I changed the code to just drop the lock while we create and
> initialize the glx display.  Once we're ready to add it to the list,
> we take the lock again.  After making sure nobody beat us to
> initializing glx on the display, we add it to the global list.  I
> think that should work.
>

Looks good to me and works well for my test cases/toolkit. Thanks.

In some of the error exits in __glXInitialize() there are some  
superfluous leftover XUnlockMutex() calls for the no longer held  
mutex. Not harmful i guess, but could be deleted.

best,
-mario