This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcj/10746] [3.3/3.4 regression] [win32] garbage collection crash in GCJ
- From: "oyvind dot harboe at zylin dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 20 Aug 2003 06:36:22 -0000
- Subject: [Bug libgcj/10746] [3.3/3.4 regression] [win32] garbage collection crash in GCJ
- References: <20030512122601.10746.oyvind.harboe@zylin.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10746
------- Additional Comments From oyvind dot harboe at zylin dot com 2003-08-20 06:36 -------
These are not breaking news, but here are the results of various things that
I've tried:
- The program does not have to be rewritten very much for the crash to go away.
This I discovered as part of my attempts to further reduce the problem.
- The crash happens almost every time in the same place(getClass()), but there
are a handful of other symptoms(null pointer exceptions, segmentation faults
elsewhere in the program).
- I haven't managed to reproduce it under Linux using GCC 3.4(or any other
version of GCC for that matter).
- It happens much more quickly when I run it from Insight than from the command
line GDB. I have not run the test from Insight under Linux.
- I compiled GCC 3.4 with disable-hash-synchronization, same problem.
- I tried to compile GCC 3.4 with disable-java-gc, but I got compilation errors.
Really what this problem needs is someone with the required Windows/GCJ
skillset to tackle it head on because it is fairly reproduceable.
Øyvind