This is the mail archive of the
java-prs@sourceware.cygnus.com
mailing list for the Java project.
Re: libgcj/67
- To: tromey at cygnus dot com
- Subject: Re: libgcj/67
- From: tromey at cygnus dot com
- Date: 8 Nov 1999 17:16:00 -0000
- Cc: java-prs at sourceware dot cygnus dot com,
- Reply-To: tromey at cygnus dot com
The following reply was made to PR libgcj/67; it has been noted by GNATS.
From: tromey@cygnus.com
To: dey@nc.fnc.fujitsu.com, java-gnats@sourceware.cygnus.com,
tromey@cygnus.com
Cc:
Subject: Re: libgcj/67
Date: 8 Nov 1999 17:13:14 -0000
Synopsis: Core dump of simple application
State-Changed-From-To: open->feedback
State-Changed-By: tromey
State-Changed-When: Mon Nov 8 09:13:14 1999
State-Changed-Why:
This is probably not a GC problem at all. I imagine you
can "cont" past the apparent GC SEGV to find the real SEGV.
In some situations the GC causes SEGVs on purpose, and then
traps them to get information (for instance it does this
when finding stack limits).
Instead I imagine this is the Solaris linker bug.
You have to use the latest GNU ld with libgcj.
This has been hashed out several times on the list,
and is probably mentioned in the FAQ (though I'm not
positive).
Please get back to me on this so I can close the PR
or investigate more fully.
http://sourceware.cygnus.com/cgi-bin/gnatsweb.pl?cmd=view&database=java&pr=67