This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
java/5986: SIGSEGV in __gcj_personality_v0
- From: jsturm at one-point dot com
- To: gcc-gnats at gcc dot gnu dot org
- Date: 17 Mar 2002 15:13:47 -0000
- Subject: java/5986: SIGSEGV in __gcj_personality_v0
- Reply-to: jsturm at one-point dot com
>Number: 5986
>Category: java
>Synopsis: SIGSEGV in __gcj_personality_v0
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Mar 17 07:16:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Jeff Sturm
>Release: gcc version 3.1 20020316 (prerelease)
>Organization:
>Environment:
Reading specs from /opt/gcc/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
Configured with: ../configure --prefix=/opt/gcc --enable-languages=c++,java --enable-threads : (reconfigured) : (reconfigured) : (reconfigured) : (reconfigured) : (reconfigured)
Thread model: posix
>Description:
The attached program fails when compiled from bytecode. Compiling from source works as expected.
This appears to be a new problem rather than a regression... 3.0.4 exhibits the same behavior.
I entered this as a frontend bug since the indications are that gcj is emitting either bad code or wrong unwind info.
>How-To-Repeat:
gcj -C CrashEH.java
gcj CrashEH.java --main=CrashEH -o CrashEH
./CrashEH
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: