Preliminary patch: New stack trace infrastructure

Mark Wielaard
Sat Jan 15 17:59:00 GMT 2005


On Mon, 2004-11-29 at 17:18 +0000, Andrew Haley wrote:
> Bryce McKinlay writes:
> > Basically, this code will give clean looking, accurate stack traces 
>  > using the DWARF2 debugging information and gcj's compiled metadata.
>  > 
>  > Key benefits:
>  > 
>  > - It gives stack traces, complete with line numbers, through interpreted 
>  > bytecode (part of this code is based on an earlier implementation from 
>  > Mark Wielaard - thanks Mark!)
>  > - It gives stack traces through shared libraries. Currently, addr2line 
>  > is still used to do this, which can be a noticeable performance problem 
>  > when it has to open big libraries like libgcj, but I plan to integrate 
>  > Casey Marshall's DWARF2 debug-info reading code soon. For now we may 
>  > wish to disable addr2line usage for applications where printStackTrace() 
>  > must be fast.
>  > - Stack trace implementation is secure: stack frame -> class association 
>  > is no longer based on mangled names, so classes wont be able to 
>  > illegally elevate their privileges just by being called the same name as 
>  > a secure class.
>  > - Stack printing looks nicer and is smarter about which frames to 
>  > include or exclude.
> This looks good, and you submitted it before the Thanksgiving
> deadline.

I really want to see this in. It will enable use to work on more GNU
Classpath integration (see new VMStackWalker runtime interface). And at
least the stack traces with line numbers through interpreted bytecode is
really nice for those quick and dirty debugging sessions. Is there a new
patch I can try out? Should I re-submit the line-number code separately?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the Java-patches mailing list