This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: GC seems to kill process
- From: Tom Tromey <tromey at redhat dot com>
- To: "Boehm, Hans" <hans dot boehm at hp dot com>
- Cc: "Andrew Haley" <aph at redhat dot com>, "Andi Vajda" <andi at osafoundation dot org>, <java at gcc dot gnu dot org>
- Date: 22 Mar 2006 15:23:11 -0700
- Subject: Re: GC seems to kill process
- References: <65953E8166311641A685BDF71D865826A236A7@cacexc12.americas.cpqcorp.net>
- Reply-to: tromey at redhat dot com
>>>>> "Hans" == Boehm, Hans <hans.boehm@hp.com> writes:
Hans> My impression was that Tom had checked in a partial workaround that uses
Hans> linker interception for thread creation? But that may not be in this
Hans> tree. (See http://gcc.gnu.org/ml/java-patches/2006-q1/msg00181.html and
Hans> related.)
It could be that this workaround causes other problems. We've
already seen it cause a problem with frysk, involving improperly
intercepting a thread created by glibc for some timer thing.
Bryce is working on a fix for this.
Andi, perhaps a 'thread apply all bt' would help, I'm not sure though.
One thing is to make sure that 'make check' in the GC build directory
works. It probably will, but it is good to isolate variables here...
Pulling out the 13212 workaround may be worth trying. There are a
few ways to do this, the simplest is to remove the code in configure
that defines GC_PTHREAD_SYM_VERSION and then do a clean rebuild.
This will take a long time, of course... there are quicker ways that
require more careful hacking around.
Tom