public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jsturm@one-point.com
To: gcc-gnats@gcc.gnu.org
Subject: java/5986: SIGSEGV in __gcj_personality_v0
Date: Sun, 17 Mar 2002 07:16:00 -0000 [thread overview]
Message-ID: <20020317151347.7747.qmail@sources.redhat.com> (raw)
>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:
next reply other threads:[~2002-03-17 15:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-17 7:16 jsturm [this message]
2002-03-20 15:46 Tom Tromey
2002-03-20 17:26 Jeff Sturm
2002-03-21 1:26 Bryce McKinlay
2002-03-21 6:46 Jeff Sturm
2002-03-27 13:26 Tom Tromey
2002-03-27 15:05 tromey
2002-03-27 15:06 Tom Tromey
2002-03-27 16:36 Alexandre Petit-Bianco
2002-03-27 16:56 Tom Tromey
2002-03-28 14:06 Jeff Sturm
2002-03-28 14:56 Alexandre Petit-Bianco
2002-03-28 16:41 tromey
2002-03-28 16:46 Tom Tromey
2002-03-28 17:26 Jeff Sturm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020317151347.7747.qmail@sources.redhat.com \
--to=jsturm@one-point.com \
--cc=gcc-gnats@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).