From: "Ananth Sowda" <asowda@gmail.com>
To: gdb@sourceware.org
Subject: Call stack trace implementation
Date: Tue, 11 Dec 2007 20:59:00 -0000 [thread overview]
Message-ID: <c92b40c80712111259i5d860224gb2db31d07bd93eaa@mail.gmail.com> (raw)
My question is on implementation of stack backtrace on architures,
MIPS and PPC. Is the implementation based on libunwind and unwind
directives in the executable? Or is it based on older code which
analyzes prologue of a function? Or a mix of both approaches?
Thanks
next reply other threads:[~2007-12-11 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 20:59 Ananth Sowda [this message]
2007-12-11 21:01 ` 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=c92b40c80712111259i5d860224gb2db31d07bd93eaa@mail.gmail.com \
--to=asowda@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