public inbox for
 help / color / mirror / Atom feed
From: Tom Tromey <>
To: Ray Ruvinskiy <>
Cc: Phil Muldoon <>,
Subject: Re: Debugging a NullPointerException in fstack
Date: Thu, 12 Jun 2008 05:44:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Ray Ruvinskiy's message of "Tue\, 10 Jun 2008 23\:03\:12 -0400")

>>>>> "Ray" == Ray Ruvinskiy <> writes:

Ray> I was able to successfully step through the code in gdb but not
Ray> to print out object contents.

Yeah, there are oddities here sometimes.  I just call the debug
printers instead:

call _Jv_Debug(obj)  # print OBJ
call _Jv_DeepDebug(obj, depth)  # print OBJ and sub-objects to DEPTH
call _Jv_StaticDeepDebug(obj, depth) # like _Jv_DeepDebug, but also
                                     # show static fields

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

I never remember what this means.  Basically the gcj support in gdb is
ok but not super.  So, you'll run into problems on occasion.

Ray> Also, gdb displayed many warnings along the following lines:

Ray> warning: Missing the separate debug info file: /usr/lib/debug/.build- 
Ray> id/fa/841219472d35412ad631ad0f0fabb78e5c1957.debug

You are missing debuginfo for various system libraries.
This is harmless unless you want to step into one of them.
Often, having info for libgcj is helpful.


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