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: Fri, 07 Dec 2001 23:16:00 -0000	[thread overview]
Message-ID: <20011208071631.4673.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: tromey@gcc.gnu.org
Cc: 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
Subject: Re: java/4639: gij HelloWorld segfaults if both HelloWorld.class and HelloWord executable is present
Date: Sat, 8 Dec 2001 08:05:10 +0100

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA1
 
 Hi,
 
 I tried to reproduce the problem with my current setup (same (gcc 
 version 3.0.2 20011014 (prerelease)) version of gcc/gcj/gij, but minor 
 updates of some other packages). Now gij doesn't dump core, but just 
 hangs, with a zombie child process:
 
 [otto@power otto]$ ps axuw | grep gij
 otto      5951  0.8  3.0  9472 7904 pts/0    S    07:55   0:00 gij 
 HelloWorld
 otto      5952  0.0  0.0     0    0 pts/0    Z    07:55   0:00 [gij 
 <defunct>]
 [otto@power otto]$
 
 
 I do not know which lib causes this different behavior. I do remember 
 though, that the core dump was of no use, since gdb on LinuxPPC doesn't 
 work with gcj/gij very well. It justs says seg fault, with no stack 
 backtrace.
 
 \Gr, Otto
 
 On vrijdag, december 7, 2001, at 08:04 , tromey@gcc.gnu.org wrote:
 
 > 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
 >
 - --
 Otto Moerbeek       otto@drijf.net
 Public Key fingerprint: 13F7 EB00 14D7 7810 88DA  CDDE DBF1 B5AB 2FB7 
 A5A3
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (Darwin)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE8Ebut2/G1qy+3paMRAuKSAKCSunS1kE4FoEP4j44e+dytXogorgCgw1oT
 r+ajy8TIjogUTMhG78TWpEs=
 =tsAs
 -----END PGP SIGNATURE-----
 


             reply	other threads:[~2001-12-08  7:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 23:16 Otto Moerbeek [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 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=20011208071631.4673.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).