StackTraceElements (Was: [kaffe] Notes on kaffe (GNU Classpath integration) todo items)

Dalibor Topic robilad at
Tue Jul 15 02:52:01 PDT 2003

Mark Wielaard wrote:
> Hi,
> On Mon, 2003-07-14 at 10:19, Helmer Krämer wrote:
>>i've got a working version of this in my local tree
>>(jetty for jdk 1.4 was working fine with it), but
>>somehow didn't get around to commit it :( Could you
>>probably post a patch of your implementation so I
>>can fix and commit it?
> With this patch the attached program gives the following stack trace:
> java.lang.NullPointerException
>    at Throw.testNull (
>    at Throw.main (
> java.lang.ArithmeticException
>    at Throw.testDivZero (
>    at Throw.main (
> java.lang.Exception: b confused
>    at Throw.a (
>    at Throw.testChain (
>    at Throw.main (
> Caused by: java.lang.Exception: d broken
>    at Throw.c (
>    at Throw.b (
>    at Throw.a (
>    ...2 more
> Caused by: java.lang.Exception: fatal error
>    at Throw.e (
>    at Throw.d (
>    at Throw.c (
>    ...4 more

nice! I hope Helmer can take a look at the patch, since he's been 
working on the same problem.

I like the way Mark's changes introduce Classpath's separation of 
VM-dependant implementation bits in VMSomething classes. That will make 
further merges of the code with Classpath easier.

> BTW how do you keep track of copyrights? I added a new copyright header
> to every file I changed, but looking through the rest of the sources
> this seems not customary.

Adding copyright information to a file is fine. When I want to know who 
wrote what, I usually use CVS and the ChangeLog, though I guess 
explicitely saying that developer X has worked on some file Y doesn't 
hurt. ;)

dalibor topic

More information about the kaffe mailing list