* [Fwd: Re: Debugging a NullPointerException in fstack]
@ 2008-06-11 7:20 Rick Moseley
0 siblings, 0 replies; only message in thread
From: Rick Moseley @ 2008-06-11 7:20 UTC (permalink / raw)
Ray Ruvinskiy wrote:
> 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?
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-06-11 4:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-06-11 7:20 [Fwd: Re: Debugging a NullPointerException in fstack] Rick Moseley
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).