From: "Andrew Burgess" <aab@cichlid.com>
To: gdb@sources.redhat.com
Subject: Re: backtrace of the current process execution
Date: Fri, 03 Dec 2004 18:55:00 -0000 [thread overview]
Message-ID: <opsif37cbn9zd2pf@mail.cichlid.com> (raw)
In-Reply-To: <je1xe74dnw.fsf@sykes.suse.de>
On Fri, 03 Dec 2004 16:14:27 +0100, Andreas Schwab <schwab@suse.de> wrote:
> laurent.marzullo@one-d.com writes:
>
>> I would like to know if there's a way to know the call stack of a
>> running
>> process into the process itself ?
>
> Try the backtrace function from <execinfo.h>.
This is handy but gives no _static_ symbols. I start with backtrace()
and then create a pipe to addr2line (part of binutils). This gives
static symbols and the exact line numbers. You could also post-process with
addr2line I suppose...
Now if it only printed arguments like gdb...
It really seems like a useful feature for a libgdb since gdb already
knows how to do it.
HTH
prev parent reply other threads:[~2004-12-03 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 15:06 laurent.marzullo
2004-12-03 15:14 ` Andreas Schwab
2004-12-03 15:20 ` Bob Rossi
2004-12-03 18:55 ` Andrew Burgess [this message]
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=opsif37cbn9zd2pf@mail.cichlid.com \
--to=aab@cichlid.com \
--cc=gdb@sources.redhat.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