This is the mail archive of the java-discuss@sourceware.cygnus.com mailing list for the GCJ project. See the GCJ home page for more information.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: stack overflow & null pointer exceptions

> From: Godmar Back <gback@cs.utah.edu>
> Date: Wed, 21 Apr 1999 10:09:16 -0600 (MDT)
> 
> Andrew, did you try the test program I sent?

Yes.

> I updated and tried it on a Linux 2.2.5/glibc2.0.7 RH 5.2 box, and it 
> still doesn't quite seem to work.
> 
> Here it is again:

<snip>

> When run with the .java frontend, I see:
> 
> gback@peerless [24](/tmp) > gcj --main=NullPointerTest NullPointerTest.java
> gback@peerless [25](/tmp) > ./a.out
> Perfectnull
> ° ... lots of garbage ...

I think that we have a problem with try ... finally in Java source
files.  I'm looking into it.

> When compiling the .class file only, I see:
> 
> gback@peerless [26](/tmp) > javac NullPointerTest.java 
> gback@peerless [27](/tmp) > gcj --main=NullPointerTest NullPointerTest.class 
> gback@peerless [28](/tmp) > ./a.out
> This is Perfect
> ° ... lots of garbage ...

I don't see any of the garbage when compiling from .class, just 
"This is Perfect".  I've absolutely no idea why this happens to 
you.

Try replacing

  String x = yuck.toLowerCase();

with

  throw new NullPointerException();

and tell me what happens.

Andrew.