public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com> 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: Tue, 18 Dec 2001 14:36:00 -0000 [thread overview] Message-ID: <20011218223601.9653.qmail@sources.redhat.com> (raw) The following reply was made to PR java/4639; it has been noted by GNATS. From: Tom Tromey <tromey@redhat.com> To: Otto Moerbeek <otto@drijf.net> Cc: gcc-gnats@gcc.gnu.org, mark@klomp.org Subject: Re: java/4639: gij HelloWorld segfaults if both HelloWorld.class and HelloWord executable is present Date: 18 Dec 2001 15:33:13 -0700 >>>>> "Otto" == Otto Moerbeek <otto@drijf.net> writes: Otto> I tried to reproduce the problem with my current setup (same Otto> (gcc version 3.0.2 20011014 (prerelease)) version of Otto> gcc/gcj/gij, but minor updates of some other packages). Now gij Otto> doesn't dump core, but just hangs, with a zombie child process: Could you try attaching to the hung process and then see what is happening? I'm guessing the problem must be system-specific. libgcj just asks the system (via libltdl) to load shared libraries. Tom
next reply other threads:[~2001-12-18 22:36 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-18 14:36 Tom 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-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=20011218223601.9653.qmail@sources.redhat.com \ --to=tromey@redhat.com \ --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: 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).