From: "Jim Blandy" <jimb@red-bean.com>
To: "Mark Kettenis" <mark.kettenis@xs4all.nl>
Cc: drow@false.org, sjackman@gmail.com, gdb-patches@sourceware.org
Subject: Re: Fix a crash when stepping and unwinding fails
Date: Wed, 22 Feb 2006 04:28:00 -0000 [thread overview]
Message-ID: <8f2776cb0602211459u434690e7vc210196ad99a7b24@mail.gmail.com> (raw)
In-Reply-To: <200602212134.k1LLY3Sq028067@elgar.sibelius.xs4all.nl>
On 2/21/06, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> But get_current_frame() should be the innermost frame when we execute
> this code. So the prologue analyzer can't be involved here. However,
> yes, it seems that step_frame_idd can end up as null_frame_id, if
> get_current_frame() is also the outermost frame at the same time.
An alternative explanation to Daniel's: the base address in the ID of
frame #0 needs to be the base of the stack frame, so that it won't
change as the function executes and does whatever pushes and pops it
has in mind. The only way to find the base of the stack frame is to
do prologue analysis or consult CFI.
prev parent reply other threads:[~2006-02-21 22:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 4:33 Daniel Jacobowitz
2006-02-21 10:01 ` Eli Zaretskii
2006-02-21 20:28 ` Mark Kettenis
2006-02-21 20:43 ` Daniel Jacobowitz
2006-02-21 20:54 ` Mark Kettenis
2006-02-21 21:03 ` Daniel Jacobowitz
2006-02-21 21:53 ` Mark Kettenis
2006-02-21 22:59 ` Daniel Jacobowitz
2006-02-22 22:00 ` Mark Kettenis
2006-02-23 2:04 ` Daniel Jacobowitz
2006-02-23 17:04 ` NZG
2006-05-17 17:59 ` Daniel Jacobowitz
2006-06-13 18:42 ` Daniel Jacobowitz
2006-06-14 12:33 ` Joel Brobecker
2006-06-16 1:16 ` Daniel Jacobowitz
2006-02-22 4:28 ` Jim Blandy [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=8f2776cb0602211459u434690e7vc210196ad99a7b24@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=sjackman@gmail.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