[Kaffe] core dump while running kaffe.

[Archie Cobbs]

Godmar Back writes:
> What's happening is that a thread holds the utf8 lock while a garbage
> collection finishes.  Since we synchronously free classes and related
> data structures, the gc thread attempts to grab the utf8 lock, resulting
> in a deadlock.  The same is possible for the stringLock, btw, despite
> the precautionary measure of giving it up before calling malloc().
> 
> Hmmm, I think I can either patch it up by having the gc thread grab
> the utf8 & string lock before it starts (just like it now grabs the 
> allocator lock), or I could get rid of the utf8 and string locks in
> favor of a global "master" allocation lock.

Why should any thread need to hold the utf8 lock for any non-trivial
length of time?  If there's no reason then we can just disable context
switches any time the utf8 lock is held.

-Archie

___________________________________________________________________________
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com