[Fwd: Re: Debugging a NullPointerException in fstack]

[Rick Moseley <rmoseley at redhat dot com>]

Ray Ruvinskiy wrote:
> Phil,
>
> Thank you very much for the tips. I have filed a bug with the debug 
> logging output.
>
> In general, I was wondering what the best way to debug gcj problems 
> is. Is it possible to make it so that when a program compiled with gcj 
> throws an exception, the stack trace is displayed, like it would be if 
> a jar file is run with Sun's jre? Is there any hope in getting gdb to 
> meaningfully debug gcj-compiled binaries?
Ray,

You can get line numbers if you edit the frysk/common/Makefile.rules and 
change the 2 lines that have "demangle=false" to "demangle=true".  But, 
this may not always work as Tom points out in his reply, sometimes 
exceptions may be lost/swallowed.  I have only had a couple of problems 
with this in my few years of debugging frysk problems though.

Rick
>