public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Otto Moerbeek <otto@drijf.net>
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: Mon, 12 May 2003 19:20:00 -0000	[thread overview]
Message-ID: <20030512191600.32582.qmail@sources.redhat.com> (raw)

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

From: Otto Moerbeek <otto@drijf.net>
To: Dara Hazeghi <dhazeghi@yahoo.com>
Cc: mark@klomp.org, tromey@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: java/4639: gij HelloWorld segfaults if both HelloWorld.class and HelloWord executable is present
Date: Mon, 12 May 2003 20:58:27 +0200

 On Monday, May 12, 2003, at 20:41 Europe/Amsterdam, Dara Hazeghi wrote:
 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 > trail&database=gcc&pr=4639
 >
 > Hello,
 >
 > this bug was last update over a year ago. Is it still a problem? With  
 > gcc 3.2, 3.3 branch and mainline (20030511) on i686-linux, the problem  
 > does not appear. Thanks,
 >
 > Dara
 
 Hi Dara,
 
 Note that I was able to reproduce this problem on my particular  
 LinuxPPC machine only. I do not have access to such a machine right  
 now, so I cannot event try to reproduce it. I know that mark@klomp.org  
 also investigated this problem but was unable to reproduce it.
 
 So go ahead and close it.
 
 Regards, Otto
 


             reply	other threads:[~2003-05-12 19:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12 19:20 Otto Moerbeek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13  6:24 steven
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:16 tromey
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=20030512191600.32582.qmail@sources.redhat.com \
    --to=otto@drijf.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=tromey@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).