This is the mail archive of the
java-prs@gcc.gnu.org
mailing list for the Java project.
[Bug libgcj/18266] GCJ: Using references drops finalizers causing all apps to eventually crash ( SIGSEGV in GC_register_finalizer_inner () )
- From: "daney at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: java-prs at gcc dot gnu dot org
- Date: 23 Sep 2008 17:40:12 -0000
- Subject: [Bug libgcj/18266] GCJ: Using references drops finalizers causing all apps to eventually crash ( SIGSEGV in GC_register_finalizer_inner () )
- References: <bug-18266-7936@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #18 from daney at gcc dot gnu dot org 2008-09-23 17:40 -------
Created an attachment (id=16396)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16396&action=view)
Possible work-around
This is a patch against 3.4.3 that we are seriously considering using
internally. The theory is: With code compiled from valid java source, it is
impossible to be GCable while holding a lock, so adding a finalizer is
redundant.
It is still not clear to me if the number of heavy_locks could grow without
bound while using the patch. We are analyzing this now...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18266