java/4639: gij HelloWorld segfaults if both HelloWorld.class and HelloWord executable is present
Otto Moerbeek
otto@drijf.net
Sat Dec 8 00:05:00 GMT 2001
-----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-----
More information about the Gcc-bugs
mailing list