public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tromey@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ian.bruce@myrealbox.com, java-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: java/5368: gcj-3.0.3 segfaults with 20 line program Date: Sun, 10 Feb 2002 16:32:00 -0000 [thread overview] Message-ID: <20020211003225.20134.qmail@sources.redhat.com> (raw) Synopsis: gcj-3.0.3 segfaults with 20 line program State-Changed-From-To: open->analyzed State-Changed-By: tromey State-Changed-When: Sun Feb 10 16:32:24 2002 State-Changed-Why: I've verified this still happens with 3.1. It crashes while trying to print an error message. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5368
next reply other threads:[~2002-02-11 0:32 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-10 16:32 tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-25 13:06 mark 2002-01-13 7:16 ian.bruce
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=20020211003225.20134.qmail@sources.redhat.com \ --to=tromey@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=ian.bruce@myrealbox.com \ --cc=java-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).