public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tromey@gcc.gnu.org
To: tromey@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/4639: gij HelloWorld segfaults if both HelloWorld.class and HelloWord executable is present
Date: Fri, 07 Dec 2001 11:16:00 -0000	[thread overview]
Message-ID: <20011207191604.25369.qmail@sources.redhat.com> (raw)

The following reply was made to PR java/4639; it has been noted by GNATS.

From: tromey@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  java-prs@gcc.gnu.org, mark@klomp.org, nobody@gcc.gnu.org, otto@drijf.net,
  tromey@gcc.gnu.org
Cc:  
Subject: Re: java/4639: gij HelloWorld segfaults if both HelloWorld.class and HelloWord executable is present
Date: 7 Dec 2001 19:04:59 -0000

 Synopsis: gij HelloWorld segfaults if both HelloWorld.class and HelloWord executable is present
 
 Responsible-Changed-From-To: unassigned->tromey
 Responsible-Changed-By: tromey
 Responsible-Changed-When: Fri Dec  7 11:04:57 2001
 Responsible-Changed-Why:
     I'm handling it.
 State-Changed-From-To: open->analyzed
 State-Changed-By: tromey
 State-Changed-When: Fri Dec  7 11:04:57 2001
 State-Changed-Why:
     I tried it with gcj 3.1 and it worked fine.
     I don't have 3.0 built right now so trying that is a pain.
     It could be a bug that was fixed since the 3.0.2 release,
     but I don't really remember anything that would affect this.
     Could you send me a gij stack trace?
     That might help.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4639&database=gcc


             reply	other threads:[~2001-12-07 19:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 11:16 tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13  6:24 steven
2003-05-12 19:20 Otto Moerbeek
2003-05-12 19:15 Dara Hazeghi
2001-12-19 12:26 Otto Moerbeek
2001-12-18 14:36 Tom Tromey
2001-12-08  2:36 Mark Wielaard
2001-12-07 23:16 Otto Moerbeek
2001-12-07 11:05 tromey
2001-10-21 12:06 otto

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=20011207191604.25369.qmail@sources.redhat.com \
    --to=tromey@gcc.gnu.org \
    --cc=gcc-prs@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).