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


I was able to successfully step through the code in gdb but not to  
print out object contents. I saw things like the following:

(gdb) p pid
$12 = Expected a negative vbase offset (old compiler?)

Also, gdb displayed many warnings along the following lines:

warning: Missing the separate debug info file: /usr/lib/debug/.build- 

warning: Missing the separate debug info file: /usr/lib/debug/.build- 

warning: Missing the separate debug info file: /usr/lib/debug/.build- 

warning: Missing the separate debug info file: /usr/lib/debug/.build- 


On 10-Jun-08, at 10:17 PM, Tom Tromey wrote:

>>>>>> "Ray" == Ray Ruvinskiy <> 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.
> Ray> Is there any hope in getting gdb to meaningfully debug
> Ray> gcj-compiled binaries?
> This should pretty much work.
> Tom

  reply	other threads:[~2008-06-11  3:04 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 [this message]
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).