This is the mail archive of the
java-prs@gcc.gnu.org
mailing list for the Java project.
[Bug libgcj/27170] Deadlock in garbage collector
- From: "Hans dot Boehm at hp dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: java-prs at gcc dot gnu dot org
- Date: 14 Apr 2006 20:51:25 -0000
- Subject: [Bug libgcj/27170] Deadlock in garbage collector
- References: <bug-27170-83@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #2 from Hans dot Boehm at hp dot com 2006-04-14 20:51 -------
Based on the thread 13 stack trace, it looks to me like we're calling dlopen
directly, when we should somehow be arranging to call GC_dlopen. GC_dlopen is
included in the GC to avoid this sort of deadlock.
(The way GC_dlopen does this is by waiting for, and then disabling, GC during
dlopen. That's not a great solution, since it can cause unneeded heap growth
in the presence of frequent dlopens. It should perhaps conditionally trigger a
GC before disabling it. But in any case, calling GC_dlopen is much better than
generating a deadlock.)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27170