From: Daniel Jacobowitz <drow@false.org>
To: "Bloch, Jack (SNL US)" <jack.bloch@siemens.com>
Cc: gdb@sourceware.org
Subject: Re: FW: gstack
Date: Wed, 07 Feb 2007 03:03:00 -0000 [thread overview]
Message-ID: <20070207030313.GA9380@nevyn.them.org> (raw)
In-Reply-To: <3D80B10873C01D47BEC71C8DE311CF1119DAD638@USNWK100MSX.ww017.siemens.net>
On Tue, Feb 06, 2007 at 10:06:37AM -0800, Bloch, Jack (SNL US) wrote:
> Perhaps I was not clear. Is there a way in GDB to display the signal
> which hit the program being attached to?
Hmm, I don't think there is. On a lot of systems there's no way to
tell. If you know inside the application, you could save it in a
global and have GDB print it - it's possible to get that to work
even if you do not have debug symbols.
> I expected that the thread apply all bt full would display parameters
> but the target binary has no debug symbols although I would have thought
> that the values would still be displayed
No, we can't display arguments without knowing their types, so we need
debug info.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-07 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 18:05 Bloch, Jack (SNL US)
2007-02-07 3:03 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-06 15:54 Bloch, Jack (SNL US)
2007-02-06 16:00 ` Daniel Jacobowitz
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=20070207030313.GA9380@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jack.bloch@siemens.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