From: Ray Ruvinskiy <rruvinsk@sybase.com>
To: frysk@sourceware.org
Subject: Debugging a NullPointerException in fstack
Date: Tue, 10 Jun 2008 07:20:00 -0000 [thread overview]
Message-ID: <F302931E-17AC-4A2B-B34C-59C1482B7EC7@sybase.com> (raw)
Hello,
I've compiled frysk on an i386 Fedora 8 system (thanks a lot to Rick
Moseley for all his previous help on IRC), and I'm attempting to play
with fstack. It seems to work on some processes (e.g., bash) but goes
down with a NullPointerException on most others (gconf, gnome-
screensaver, others).
I was wondering whether this was a known issue and if not, what the
best way to debug this would be. There is no stack trace displayed, so
I'm not sure where the NPE is actually coming from. I was wondering if
it was possible to compile frysk in a way that would make it more
amenable to being debugged? Also, what is the recommended way to
debug? gdb, printfs?
Thanks,
Ray
next reply other threads:[~2008-06-09 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 7:20 Ray Ruvinskiy [this message]
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
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=F302931E-17AC-4A2B-B34C-59C1482B7EC7@sybase.com \
--to=rruvinsk@sybase.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).