public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Rick Moseley <rmoseley@redhat.com>
To: frysk <frysk@sourceware.org>
Subject: [Fwd: Re: Debugging a NullPointerException in fstack]
Date: Wed, 11 Jun 2008 07:20:00 -0000	[thread overview]
Message-ID: <484F5007.4020408@redhat.com> (raw)

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
>

                 reply	other threads:[~2008-06-11  4:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=484F5007.4020408@redhat.com \
    --to=rmoseley@redhat.com \
    --cc=frysk@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).