This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
java/910: gcj compiler crashes when compiling initializer statement without paranthesis after constructor
- To: gcc-gnats at gcc dot gnu dot org
- Subject: java/910: gcj compiler crashes when compiling initializer statement without paranthesis after constructor
- From: simon dot brenner at home dot se
- Date: 27 Nov 2000 20:51:12 -0000
- Reply-To: simon dot brenner at home dot se
>Number: 910
>Category: java
>Synopsis: gcj compiler crashes when compiling initializer statement without paranthesis after constructor
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: ice-on-illegal-code
>Submitter-Id: net
>Arrival-Date: Mon Nov 27 12:56:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator: simon.brenner@home.se
>Release: 2.96 20000731 (Red Hat Linux 7.0)
>Organization:
>Environment:
>Description:
When I give the gcj Java compiler the source file, it prints an error message, and then crashes. The problem was solved when typing the parantheses after the constructor name (TextAreaPeer).
>How-To-Repeat:
I have seen the same problem when compiling other programs that didn't have parantheses after constructors.
Just compile the source file with:
gcj -o Beeper --main=Beeper Beeper.java
and watch the compiler dump...
>Fix:
Tell stupid lamers like me not to write incorrect code :)
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: unknown; name="Beeper.java"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Beeper.java"
aW1wb3J0IGphdmEuYXd0Lio7CmltcG9ydCBqYXZhLmF3dC5ldmVudC4qOwppbXBvcnQgamF2YS5h
d3QucGVlci4qOwoKY2xhc3MgYXd0QXBwIGV4dGVuZHMgV2luZG93UGVlcgp7CglUZXh0QXJlYVBl
ZXIgdHh0OwoJCglwdWJsaWMgc3RhdGljIHZvaWQgbWFpbihTdHJpbmdbXSBhcmdzKQoJewoJCXR4
dD1uZXcgVGV4dEFyZWFQZWVyOwoJCWFkZCgiQ2VudGVyIiwgdHh0KTsKCQkKCQl0aGlzLmFkZFdp
bmRvd0xpc3RlbmVyKHRoaXMpOwoJfQp9Cg==