public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/18266] SIGSEGV in GC_register_finalizer_inner ()
Date: Wed, 08 Mar 2006 19:27:00 -0000 [thread overview]
Message-ID: <20060308192735.26414.qmail@sourceware.org> (raw)
In-Reply-To: <bug-18266-7936@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from tromey at gcc dot gnu dot org 2006-03-08 19:27 -------
I've been looking into this a bit.
The current problem I see is that the heavyweight lock stuff
relies on the GC. This won't interact well with the current
code in natReference.cc, as those data structures are not scanned.
Also, I do think that both calls to _Jv_RegisterFinalizer in
Reference::create are problematic. The first call registers a finalizer
for the Reference, the second for the referent. But, there is nothing
preventing a subclass of Reference from having a finalizer; or from
user code acquiring a heavy lock on a Reference object. So, all
cases have to be handled here.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18266
next parent reply other threads:[~2006-03-08 19:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18266-7936@http.gcc.gnu.org/bugzilla/>
2006-03-08 19:27 ` tromey at gcc dot gnu dot org [this message]
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
2008-09-23 23:39 ` Hans dot Boehm at hp dot com
2008-09-26 15:58 ` daney at gcc dot gnu dot org
2004-11-01 17:21 [Bug libgcj/18266] New: SIGSEGV in GC_register_finalizer_inner () ovidr at users dot sourceforge dot net
2004-11-01 17:22 ` [Bug libgcj/18266] " ovidr at users dot sourceforge dot net
2004-11-01 20:44 ` Hans dot Boehm at hp dot com
2004-11-01 22:08 ` ovidr at users dot sourceforge dot net
2004-11-08 3:00 ` ovidr at users dot sourceforge dot net
2004-11-08 19:56 ` Hans dot Boehm at hp dot com
2004-11-08 20:27 ` ovidr at users dot sourceforge dot net
2004-11-25 1:50 ` Hans dot Boehm at hp dot com
2004-11-25 3:25 ` tromey at gcc dot gnu dot org
2004-11-25 3:26 ` tromey at gcc dot gnu dot org
2004-12-02 13:43 ` pinskia at gcc dot gnu dot org
2005-05-17 20:40 ` daney at gcc dot gnu dot org
2005-05-17 20:47 ` pinskia at gcc dot gnu dot org
2005-06-08 21:14 ` ovidr at users dot sourceforge dot net
2005-06-09 5:11 ` Hans dot Boehm at hp dot com
2005-06-20 16:25 ` ovidr at users dot sourceforge dot net
2005-07-19 15:06 ` ovidr at users dot sourceforge dot net
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=20060308192735.26414.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).