sablevm-developer

[Sablevm-developer] Bug

[Archie C. <ar...@de...>]

Maybe I'm just being stupid, but how do you file a new bug on the
SableVM bug site on SourceForge? It seems like it's read-only...

Anyway, here's the bug:

    class LineNum {
	public static void main (String args[]) {
	    try {
		    // blank line
		    // blank line
		    // blank line
		    ((Object)null).hashCode();
	    }
	    catch (Exception c) {
		    c.printStackTrace();
	    }
	}
    }

This program prints:

    $ sablevm LineNum
    java.lang.NullPointerException
	    at LineNum.main(LineNum.java:3)
	    at java.lang.VirtualMachine.invokeMain(VirtualMachine.java)
	    at java.lang.VirtualMachine.main(VirtualMachine.java:88)

Notice the "LineNum.java:3" -- that should be "LineNum.java:7" instead.

-Archie

__________________________________________________________________________
Archie Cobbs     *     Packet Design     *     http://www.packetdesign.com

[Sablevm-developer] Daily break;-)

[Etienne M. G. <eti...@uq...>]

On Mon, Aug 19, 2002 at 10:24:39AM -0700, Archie Cobbs wrote:
> Maybe I'm just being stupid, but how do you file a new bug on the
> SableVM bug site on SourceForge? It seems like it's read-only...

There should be a "submit new" link somewhere on the bug tracker page.
If you get to it, please file a bug report about the absence of a
direct link for bug submission on the sablevm web page.

> Anyway, here's the bug:

I'll investigate this after my thesis.  Hint: Have you checked the
generated "line number table" using "javap -c -l"? (Probably, but just
checking...)

Also, I've checked in the xxx_Runtime.c patch into CVS, and added your
name in AUTHORS; I assume you agree to license your patch under the
LGPL, right? :-)

The CVS code also has the _svmf_iflush() calls in place, in case
somebody wants to experiment inline-threading on processors with
distinct instr. and data caches.

To build the CVS code, you need to run the following:

$ aclocal ; libtoolize ; autoconf ; autoheader ; automake --foreign -a

using the latest GNU auto tools.

Have fun!

Etienne

-- 
Etienne M. Gagnon                    http://www.info.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/

[Sablevm-developer] Re: Daily break;-)

[Archie C. <ar...@de...>]

Etienne M. Gagnon writes:
> > Maybe I'm just being stupid, but how do you file a new bug on the
> > SableVM bug site on SourceForge? It seems like it's read-only...
> 
> There should be a "submit new" link somewhere on the bug tracker page.
> If you get to it, please file a bug report about the absence of a
> direct link for bug submission on the sablevm web page.

Yep, found it - I was just being stupid :-)

> I'll investigate this after my thesis.  Hint: Have you checked the
> generated "line number table" using "javap -c -l"? (Probably, but just
> checking...)

No, but it was compiled with jikes.. and kaffe gets the line number right
when running the same class :-)

> Also, I've checked in the xxx_Runtime.c patch into CVS, and added your
> name in AUTHORS; I assume you agree to license your patch under the
> LGPL, right? :-)

Yes.

FYI, when you (or anyone) has more time, an interesting thing to try
is to run the kaffe regression suite using 'sablevm' as the java VM
instead of kaffe (just edit tests/regression/TestScript).

There are a lot of differences, many of which point to unimplemented
features in SableVM but at least a few are bugs. Also, the kaffe 
regression suite has a lot of tests for weird corner cases having
to do with threads, classloaders, etc.

Presumably you don't want bug reports for all the unimplemented stuff..

Thanks,
-Archie

__________________________________________________________________________
Archie Cobbs     *     Packet Design     *     http://www.packetdesign.com