From: paawan oza <paawan1982@yahoo.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>,
John Yates <jyates@netezza.com>
Subject: Re: Backtrace library?
Date: Fri, 21 Aug 2009 15:46:00 -0000 [thread overview]
Message-ID: <229353.81964.qm@web112508.mail.gq1.yahoo.com> (raw)
In-Reply-To: <0C8E40D1B3E28947A3EA5E185EF1C9B2AF5FA19AF4@CORP-EXCH01.netezza.com>
I think backtrace function of glibc internally use unwind library interface to get backtrace.
unwind library interface may be used.
I am not sure exactly how gdb reads stack (just walk through esp/ebp or some other way)
Regards,
Oza.
--- On Fri, 8/21/09, John Yates <jyates@netezza.com> wrote:
> From: John Yates <jyates@netezza.com>
> Subject: Backtrace library?
> To: "gdb@sourceware.org" <gdb@sourceware.org>
> Date: Friday, August 21, 2009, 1:57 AM
> Assuming I have an elf image compiled
> with full debugging information is there any library I can
> use to get a gdb-style backtrace with sourc path and line
> number rather than the C library's rather Spartan version?
>
> /john
>
next prev parent reply other threads:[~2009-08-21 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 21:17 John Yates
2009-08-21 7:48 ` Paul Pluzhnikov
2009-08-21 15:46 ` paawan oza [this message]
2009-08-27 14:35 ` Christophe-Marie Duquesne
2009-08-27 15:45 ` John Yates
2009-08-27 17:56 ` Christophe-Marie Duquesne
2009-08-28 15:54 ` Pierre Muller
2009-08-28 16:03 ` Eli Zaretskii
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=229353.81964.qm@web112508.mail.gq1.yahoo.com \
--to=paawan1982@yahoo.com \
--cc=gdb@sourceware.org \
--cc=jyates@netezza.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