From: Joel Brobecker <brobecker@adacore.com>
To: Martin Schr?der <gschroeder@onlinehome.de>
Cc: gdb@sourceware.org
Subject: Re: Examining copied stack contents
Date: Mon, 05 Jul 2010 20:27:00 -0000 [thread overview]
Message-ID: <20100705202649.GI2928@adacore.com> (raw)
In-Reply-To: <DD285D3CBDE54AA99CE9251DAF47FA6E@igor>
There are several possible ways to do callstack unwinding on each
architecture. The prefered way is to rely on DWARF frame info, but
we otherwise fallback on other methods (either native unwinding
info, or if all else fails, prologue parsing). That's why the GDB
code for each architecture registers "sniffers" which will tell GDB
for each frame which unwinder would be best to use. The result also
depends on the type of frame, since signal frames often require their
own unwinder.
I recommend that you have a look at i386-tdep.c, and in particular
the various functions specified in the i386_frame_unwind structure.
That should help you find out what is actually going on inside GDB.
--
Joel
next prev parent reply other threads:[~2010-07-05 20:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-03 10:48 Martin Schröder
2010-07-05 4:54 ` support biarch gcore? Jon Zhou
2010-07-05 7:12 ` Jan Kratochvil
2010-07-05 11:55 ` Mark Kettenis
2010-07-06 20:48 ` Ulrich Weigand
2010-07-06 21:29 ` Mark Kettenis
2010-07-07 12:30 ` Ulrich Weigand
2010-07-08 2:35 ` Jon Zhou
2010-07-08 11:17 ` Ulrich Weigand
2010-07-08 4:47 ` H.J. Lu
2010-07-08 5:05 ` H.J. Lu
2010-07-08 11:15 ` Ulrich Weigand
2010-07-08 13:52 ` H.J. Lu
2010-07-21 22:45 ` Joseph S. Myers
2010-07-05 18:50 ` Examining copied stack contents Petr Hluzín
2010-07-05 20:18 ` Martin Schröder
2010-07-05 20:27 ` Joel Brobecker [this message]
2010-07-07 17:29 ` Martin Schröder
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=20100705202649.GI2928@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=gschroeder@onlinehome.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).