[Kaffe] core dump while running kaffe.
gback at cs.utah.edu
Mon Mar 22 15:06:17 PST 1999
That wouldn't work with native threads or on an smp where disabling
switches is impossible or very expensive.
> 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 Cobbs * Whistle Communications, Inc. * http://www.whistle.com
More information about the kaffe