public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jeff Sturm <jsturm@one-point.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/5986: SIGSEGV in __gcj_personality_v0 Date: Thu, 21 Mar 2002 06:46:00 -0000 [thread overview] Message-ID: <20020321144606.13693.qmail@sources.redhat.com> (raw) The following reply was made to PR java/5986; it has been noted by GNATS. From: Jeff Sturm <jsturm@one-point.com> To: Bryce McKinlay <bryce@waitaki.otago.ac.nz> Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: java/5986: SIGSEGV in __gcj_personality_v0 Date: Thu, 21 Mar 2002 09:38:03 -0500 (EST) On Thu, 21 Mar 2002, Bryce McKinlay wrote: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5986 > > This test case works-for-me on both x86 and PPC: > > $ gcj CrashEH.java --main=CrashEH -O2 > $ ./a.out > cleanup > ok I apologize for the faulty instructions. (Writing a good PR is hard!) Compile/run the example from bytecode: [jsturm@omega tmp]$ gcj CrashEH.class -o CrashEH --main=CrashEH [jsturm@omega tmp]$ ./CrashEH Segmentation fault It makes no difference whether I use javac or gcj -C to compile the source. Jeff
next reply other threads:[~2002-03-21 14:46 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-21 6:46 Jeff Sturm [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-28 17:26 Jeff Sturm 2002-03-28 16:46 Tom Tromey 2002-03-28 16:41 tromey 2002-03-28 14:56 Alexandre Petit-Bianco 2002-03-28 14:06 Jeff Sturm 2002-03-27 16:56 Tom Tromey 2002-03-27 16:36 Alexandre Petit-Bianco 2002-03-27 15:06 Tom Tromey 2002-03-27 15:05 tromey 2002-03-27 13:26 Tom Tromey 2002-03-21 1:26 Bryce McKinlay 2002-03-20 17:26 Jeff Sturm 2002-03-20 15:46 Tom Tromey 2002-03-17 7:16 jsturm
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=20020321144606.13693.qmail@sources.redhat.com \ --to=jsturm@one-point.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).