This is the mail archive of the
java-prs@sourceware.cygnus.com
mailing list for the Java project.
Re: libgcj/93: GC causes core dump in gcj-compiled programs
- To: tromey at cygnus dot com
- Subject: Re: libgcj/93: GC causes core dump in gcj-compiled programs
- From: Jeff Sturm <jsturm at sigma6 dot com>
- Date: 13 Nov 1999 15:30:00 -0000
- Cc: java-prs at sourceware dot cygnus dot com,
- Reply-To: Jeff Sturm <jsturm at sigma6 dot com>
The following reply was made to PR libgcj/93; it has been noted by GNATS.
From: Jeff Sturm <jsturm@sigma6.com>
To: Tom Tromey <tromey@cygnus.com>
Cc: java-gnats@sourceware.cygnus.com
Subject: Re: libgcj/93: GC causes core dump in gcj-compiled programs
Date: Sat, 13 Nov 1999 10:23:13 -0500 (EST)
On Fri, 12 Nov 1999, Tom Tromey wrote:
> FWIW, this doesn't happen to me with my current build.
> Does it still happen for you?
> (Offhand I don't recall how old my gcc is. Maybe that has some effect.)
Probably. I was using the gcc trunk. Perhaps I should have filed the PR
for gcj.
As a workaround I commented out all the marking code in libjava/boehm.cc,
so the GC scans all Java objects conservatively. My tests ran fine
afterwards. This suggests that something was wrong in reflection, on
which the marking code depends. So perhaps something changed in the class
layout, or gcj is really generating incorrect code... I'm not sure.
Jeff