public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "daney at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/18266] GCJ: Using references drops finalizers causing all apps to eventually crash  ( SIGSEGV in GC_register_finalizer_inner () )
Date: Tue, 23 Sep 2008 17:40:00 -0000	[thread overview]
Message-ID: <20080923174012.22285.qmail@sourceware.org> (raw)
In-Reply-To: <bug-18266-7936@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2008-09-23 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-18266-7936@http.gcc.gnu.org/bugzilla/>
2006-03-08 19:27 ` [Bug libgcj/18266] SIGSEGV in GC_register_finalizer_inner () tromey at gcc dot gnu dot org
2006-11-03 22:58 ` [Bug libgcj/18266] GCJ: Using references drops finalizers causing all apps to eventually crash ( SIGSEGV in GC_register_finalizer_inner () ) r_ovidius at eml dot cc
2008-09-22 20:08 ` daney at gcc dot gnu dot org
2008-09-22 23:56 ` daney at gcc dot gnu dot org
2008-09-23 17:40 ` daney at gcc dot gnu dot org [this message]
2008-09-23 23:39 ` Hans dot Boehm at hp dot com
2008-09-26 15:58 ` daney at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080923174012.22285.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).