From: Daniel Jacobowitz <drow@false.org>
To: Ashwin Bharambe <ashwinb@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Programmatic access to stack traces in C or C++ programs
Date: Fri, 20 Oct 2006 14:27:00 -0000 [thread overview]
Message-ID: <20061020142738.GC28258@nevyn.them.org> (raw)
In-Reply-To: <3ef5826d0610200541g4804ec15sc2b3167b455c735e@mail.gmail.com>
On Fri, Oct 20, 2006 at 08:41:07AM -0400, Ashwin Bharambe wrote:
> Sweet. Thanks Daniel for pointing me to libunwind.. Now, given the
> instruction pointer and stack pointer values, do you think I can use
> some parts of gdb code to dump out a more readable version of the
> stackframe? It would be _really_ nice if I could dump out argument
> values as well, but I suspect that might be much harder.
GDB is really not set up to reuse this way.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-20 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 2:27 Ashwin Bharambe
2006-10-20 3:10 ` Neo Jia
2006-10-20 3:13 ` Daniel Jacobowitz
2006-10-20 12:41 ` Ashwin Bharambe
2006-10-20 14:27 ` Daniel Jacobowitz [this message]
2006-10-20 20:18 ` Michael Snyder
2006-10-20 21:47 ` David Carlton
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=20061020142738.GC28258@nevyn.them.org \
--to=drow@false.org \
--cc=ashwinb@gmail.com \
--cc=gdb@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