public inbox for
 help / color / mirror / Atom feed
From: Ray Ruvinskiy <>
To: Phil Muldoon <>
Subject: Re: Debugging a NullPointerException in fstack
Date: Wed, 11 Jun 2008 02:17:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


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?



On 10-Jun-08, at 3:20 AM, Phil Muldoon wrote:

> Ray Ruvinskiy wrote:
>> Hello,
> Hi Ray,
> Thanks for the report. The first thing I would do is to file a bug at:
> To track the issue. I would not worry too much about semantics of  
> the bug reports, or whether it is a duplicate. The report itself is  
> valuable even if it does already exist. Typically when I file a  
> report I'll put in whether I run Frysk from RPM, or built from  
> source. And what OS you are running it on. And just include all the  
> output of the tool. If fstack is failing with an NPE on some  
> processes not others, it is most certainly a programming error  
> somewhere.
> From a more in depth perspective, if you build from source, you can  
> test the sanity of your environment particular to your system by  
> running the Frysk testsuite. I normally cd into frysk-core/ and  
> run ./TestRunner. You can do this from each sub-component, or if you  
> like, run make check instead.
> Lastly if you want to jump straight in, fix the problem yourself,  
> and submit a patch, try turning debug logging on with something like:
> ./frysk/bindir/fstack -debug frysk=FINE 1234
> But even if you do try to hack on it yourself, please do file a bug  
> and assign it to yourself. We know who is hacking on what then.
> Best of luck and hope to see you on IRC!
> Regards
> Phil Muldoon

  reply	other threads:[~2008-06-11  1:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10  7:20 Ray Ruvinskiy
2008-06-10  7:40 ` Phil Muldoon
2008-06-11  2:17   ` Ray Ruvinskiy [this message]
2008-06-11  3:04     ` Tom Tromey
2008-06-11  4:10       ` Ray Ruvinskiy
2008-06-12  5:44         ` Tom Tromey
2008-06-11 13:20       ` Phil Muldoon

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:

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

  git send-email \ \ \ \ \

* 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).