From: Daniel Jacobowitz <drow@false.org>
To: Paul Breed <pbreed@netburner.com>
Cc: gdb@sourceware.org
Subject: Re: Frame unwind and the sentinal frame.
Date: Fri, 30 Jun 2006 19:05:00 -0000 [thread overview]
Message-ID: <20060629022658.GA32372@nevyn.them.org> (raw)
In-Reply-To: <6.2.3.4.2.20060628164353.060d3530@mail.netburner.com>
On Wed, Jun 28, 2006 at 04:47:36PM -0700, Paul Breed wrote:
> I'm working on a GDB remote stub for the coldfire. (Think 68K)
>
> When the system does a bt (back trace )
> or an MI stack-info-depth
>
> It eventually walks off the end of the frames and generates an error message
>
> Previous frame inner to this frame (corrupt stack?)
>
> How is GDB supposed to detect the "Last" frame in the stack,
The right answer depends on your architecture: a NULL frame pointer, a
zero PC, or a function marked as an ELF entry point are all reasonable
choices. Then, of course, you have to make sure GDB agrees with you on
the proper convention. As you'll see in the list archives that can
sometimes be a bit iffy.
> I think this is called the sentinal frame?
No - that's at the other end of the stack, actually. It's more of a
GDB internal detail.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-06-29 2:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 18:42 Paul Breed
2006-06-30 19:05 ` 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=20060629022658.GA32372@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=pbreed@netburner.com \
/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