From: Daniel Jacobowitz <drow@false.org>
To: Ananth Sowda <asowda@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Call stack trace implementation
Date: Tue, 11 Dec 2007 21:01:00 -0000 [thread overview]
Message-ID: <20071211210127.GA18958@caradoc.them.org> (raw)
In-Reply-To: <c92b40c80712111259i5d860224gb2db31d07bd93eaa@mail.gmail.com>
On Tue, Dec 11, 2007 at 12:59:33PM -0800, Ananth Sowda wrote:
> 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?
Both prologue analysis and call frame information. Libunwind is not
used except on IA64; GDB has its own support for DWARF-2 unwind tables.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-12-11 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 20:59 Ananth Sowda
2007-12-11 21:01 ` Daniel Jacobowitz [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=20071211210127.GA18958@caradoc.them.org \
--to=drow@false.org \
--cc=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