* Call stack trace implementation
@ 2007-12-11 20:59 Ananth Sowda
2007-12-11 21:01 ` Daniel Jacobowitz
0 siblings, 1 reply; 2+ messages in thread
From: Ananth Sowda @ 2007-12-11 20:59 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Call stack trace implementation
2007-12-11 20:59 Call stack trace implementation Ananth Sowda
@ 2007-12-11 21:01 ` Daniel Jacobowitz
0 siblings, 0 replies; 2+ messages in thread
From: Daniel Jacobowitz @ 2007-12-11 21:01 UTC (permalink / raw)
To: Ananth Sowda; +Cc: gdb
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-12-11 21:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-12-11 20:59 Call stack trace implementation Ananth Sowda
2007-12-11 21:01 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox