Re: gcj/232: segmentation violation at except.c:2180

[Bryce McKinlay <bryce at albatross dot co dot nz>]

The following reply was made to PR gcj/232; it has been noted by GNATS.

From: Bryce McKinlay <bryce@albatross.co.nz>
To: fegray@uiuc.edu
Cc: java-gnats@sourceware.cygnus.com
Subject: Re: gcj/232: segmentation violation at except.c:2180
Date: Mon, 22 May 2000 11:24:10 +1200

 fegray@uiuc.edu wrote:
 
 > Download jetty.tar.gz (attached), unpack it, cd jetty,
 > and execute the script called run-test.  If your luck is as
 > bad as mine, you will see the following output:
 
 I think this a case of the bytecode front end failing to detect an error
 condition, and crashing instead of reporting an error.
 
 If I compile the jetty package from source code, I get:
 
 ./com/mortbay/Base/CodeException
 ./com/mortbay/Base/DateCache
 ./com/mortbay/Base/Code.java:93: Type `java.applet.Applet' not found in the
 declaration of the argument `appl' of method `initParamsFromApplet'.
     public static void initParamsFromApplet(java.applet.Applet appl)
                                             ^
 gcj: Internal compiler error: program jc1 got fatal signal 11
 ./com/mortbay/Base/Frame
 ./com/mortbay/Base/Log
 ./com/mortbay/Base/Log.java:137: Type `java.applet.Applet' not found in the
 declaration of the argument `appl' of method `initParamsFromApplet'.
     public static void initParamsFromApplet(java.applet.Applet appl)
                                             ^
 1 error
 ./com/mortbay/Base/Test
 ./com/mortbay/Base/Code.java:93: Type `java.applet.Applet' not found in the
 declaration of the argument `appl' of method `initParamsFromApplet'.
     public static void initParamsFromApplet(java.applet.Applet appl)
                                             ^
 gcj: Internal compiler error: program jc1 got fatal signal 11
 
 
 ...etc...
 
 libgcj does not hava a java.applet.Applet (although you could probibly bring the
 package in from classpath without too much trouble)
 
 > These classes compiled correctly with gcj 2.95.2+patches.
 
 Hmm... are you sure? Maybe it was just failing to detect the error, and generating
 bad code?
 
 regards
 
   [ bryce ]