* w32 stack sniffing/unwinding and backtrace improvement
@ 2011-08-01 13:59 LRN
0 siblings, 0 replies; only message in thread
From: LRN @ 2011-08-01 13:59 UTC (permalink / raw)
To: gdb
Which unwinder and sniffers are responsible for w32 stack unwinding
(like, when printing a frame info or a backtrace)?
I have an idea to fetch the function address from the stack as a struct
_EXCEPTION_RECORD, but i need to find the code that parses the frame. If
i succeed, it will allow for more complete backtrace in cases where gdb
is used as a JIT (in MS sense of that acronym) debugger and attaches to
a process that had its stack already mangled by the OS exception handler.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-08-01 13:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-08-01 13:59 w32 stack sniffing/unwinding and backtrace improvement LRN
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).