Re: Still crashes in GSLazyRecursiveLock

[David Ayers]

Philip Mötteli wrote:

> It seems, that by autoreleasing those locks, we just have postponed the 
> problem:

My assumption derived from looking at the stack was indeed wrong.  Now 
that I had the chance to debug it, I found the real problem.

GSLazy*Lock -init implementations did not call [super init] before 
releasing the receiver, which it does if the application is 
multithreaded to return an NS*Lock.  GNUstep's implementation of NS*Lock 
-dealloc is able to handle partially initialized NSLock instances so we 
never noticed.

I've checked in a fix which always calls [super init].  Please update 
and try again.  My tests show that it should work now.

Cheers,
David