From: Phil Muldoon <pmuldoon@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Ray Ruvinskiy <rruvinsk@sybase.com>, frysk@sourceware.org
Subject: Re: Debugging a NullPointerException in fstack
Date: Wed, 11 Jun 2008 13:20:00 -0000 [thread overview]
Message-ID: <484F7CB4.8030706@redhat.com> (raw)
In-Reply-To: <m34p80zpeo.fsf@fleche.redhat.com>
Tom Tromey wrote:
>>>>>> "Ray" == Ray Ruvinskiy <rruvinsk@sybase.com> writes:
>>>>>>
>
> Ray> Is it possible to make it so that when a program compiled with
> Ray> gcj throws an exception, the stack trace is displayed, like it
> Ray> would be if a jar file is run with Sun's jre?
>
> This should work in general. I think in some places frysk swallows
> exceptions or does not print traces.
>
Can you please file a bug against the tool/component if you know of such
a case?
Thanks
Phil
prev parent reply other threads:[~2008-06-11 7:20 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
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 [this message]
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=484F7CB4.8030706@redhat.com \
--to=pmuldoon@redhat.com \
--cc=frysk@sourceware.org \
--cc=rruvinsk@sybase.com \
--cc=tromey@redhat.com \
/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).