[Bug 6937] New: [2003-05-13] Segfault when deriving a class from another nested class
gcc-bugzilla@gcc.gnu.org
gcc-bugzilla@gcc.gnu.org
Wed May 21 17:31:00 GMT 2003
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6937
Summary: [2003-05-13] Segfault when deriving a class from another
nested class
Product: gcc
Version: unknown
Status: RESOLVED
Severity: major
Priority: P3
Component: java
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: konqueror@gmx.de
CC: dhazeghi@stanford.edu,dhazeghi@yahoo.com,gcc-
bugs@gcc.gnu.org,giovannibajo@libero.it,konqueror@gmx.de
,steven@gcc.gnu.org
When compiling the attached two files with
gcj -C Container.java Derived.java
the compiler segfaults.
Release:
CVS 20020605
Environment:
Debian Sid
How-To-Repeat:
gcj -C Container.java Derived.java
------- Additional Comments From dhazeghi@yahoo.com 2003-12-05 12:39 -------
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: konqueror@gmx.de, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: java/6937: Segfault when deriving a class from another nested class
Date: Mon, 12 May 2003 12:39:59 -0700
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
trail&database=gcc&pr=6937
Hello,
could the submitter please confirm if this problem still occurs with
gcc 3.3 prerelease or mainline cvs? On both I get errors compiling:
./Container.java:1: Class `Container' already defined in
Container.java:1.
public class Container
^
./Container.java:5: confused by earlier errors, bailing out
bash-2.04$ /tmp/dara1/bin/gcj -C Container.java Derived.java
./Container.java:1: error: Class `Container' already defined in
Container.java:1.
public class Container
^
./Container.java:5: confused by earlier errors, bailing out
Thanks,
Dara
------- Additional Comments From steven@gcc.gnu.org 2003-13-05 06:36 -------
State-Changed-From-To: open->feedback
State-Changed-Why: Dara has asked for feedback
------- Additional Comments From dhazeghi@stanford.edu 2003-13-05 10:13 -------
From: Dara Hazeghi <dhazeghi@stanford.edu>
To: Michael Koch <konqueror@gmx.de>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/6937: Segfault when deriving a class from another nested class
Date: Tue, 13 May 2003 10:13:12 -0700
On Tuesday, May 13, 2003, at 03:35 AM, Michael Koch wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Am Montag, 12. Mai 2003 22:04 schrieben Sie:
>> Begin forwarded message:
>>> From: Dara Hazeghi <dhazeghi@yahoo.com>
>>> Date: Mon May 12, 2003 12:39:59 PM US/Pacific
>>> To: konqueror@gmx.de, gcc-gnats@gcc.gnu.org
>>> Subject: Re: java/6937: Segfault when deriving a class from
>>> another nested class
>>>
>>> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
>>> trail&database=gcc&pr=6937
>>>
>>> Hello,
>>>
>>> could the submitter please confirm if this problem still occurs
>>> with gcc 3.3 prerelease or mainline cvs? On both I get errors
>>> compiling:
>>>
>>> ./Container.java:1: Class `Container' already defined in
>>> Container.java:1.
>>> public class Container
>>> ^
>>> ./Container.java:5: confused by earlier errors, bailing out
>>> bash-2.04$ /tmp/dara1/bin/gcj -C Container.java Derived.java
>>> ./Container.java:1: error: Class `Container' already defined in
>>> Container.java:1.
>>> public class Container
>>> ^
>>> ./Container.java:5: confused by earlier errors, bailing out
>>>
>>> Thanks,
>>>
>>> Dara
>
> Yes I still get the segfault with trunk-cvs from 20030513.
>
> But I do get an error with JDK 1.4.1 now too. My testcase is obviously
> wrong. I think this can be closed.
Do you just want to close it, or mark it as an ICE on illegal code?
Thanks,
Dara
------- Additional Comments From konqueror@gmx.de 2003-13-05 20:03 -------
From: Michael Koch <konqueror@gmx.de>
To: Dara Hazeghi <dhazeghi@stanford.edu>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/6937: Segfault when deriving a class from another nested class
Date: Tue, 13 May 2003 20:03:23 +0200
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Dienstag, 13. Mai 2003 19:13 schrieb Dara Hazeghi:
> On Tuesday, May 13, 2003, at 03:35 AM, Michael Koch wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Am Montag, 12. Mai 2003 22:04 schrieben Sie:
> >> Begin forwarded message:
> >>> From: Dara Hazeghi <dhazeghi@yahoo.com>
> >>> Date: Mon May 12, 2003 12:39:59 PM US/Pacific
> >>> To: konqueror@gmx.de, gcc-gnats@gcc.gnu.org
> >>> Subject: Re: java/6937: Segfault when deriving a class from
> >>> another nested class
> >>>
> >>> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-
> >>> trail&database=3Dgcc&pr=3D6937
> >>>
> >>> Hello,
> >>>
> >>> could the submitter please confirm if this problem still occurs
> >>> with gcc 3.3 prerelease or mainline cvs? On both I get errors
> >>> compiling:
> >>>
> >>> ./Container.java:1: Class `Container' already defined in
> >>> Container.java:1.
> >>> public class Container
> >>> ^
> >>> ./Container.java:5: confused by earlier errors, bailing out
> >>> bash-2.04$ /tmp/dara1/bin/gcj -C Container.java Derived.java
> >>> ./Container.java:1: error: Class `Container' already defined in
> >>> Container.java:1.
> >>> public class Container
> >>> ^
> >>> ./Container.java:5: confused by earlier errors, bailing out
> >>>
> >>> Thanks,
> >>>
> >>> Dara
> >
> > Yes I still get the segfault with trunk-cvs from 20030513.
> >
> > But I do get an error with JDK 1.4.1 now too. My testcase is
> > obviously wrong. I think this can be closed.
>
> Do you just want to close it, or mark it as an ICE on illegal code?
> Thanks,
Just close it. I think I remember that Tom said that an ICE on illegal=20
code is okay.
Michael
=2D --=20
Homepage: http://www.worldforge.org/
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+wTNsWSOgCCdjSDsRAoFiAJ4iT0Hjtrfw6ZM/lc37m39dFjq2OgCeOgme
ujFxheUeRUa7RiUHO/s7DdU=3D
=3DazXx
=2D----END PGP SIGNATURE-----
------- Additional Comments From giovannibajo@libero.it 2003-14-05 10:36 -------
State-Changed-From-To: feedback->analyzed
State-Changed-Why: No, this should not be closed. An ICE is never an
accepted behaviour, it is a bug in the compiler, which
must be fixed.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the Gcc-bugs
mailing list