From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc, frame] Always check for unsaved PC
Date: Thu, 11 Jan 2007 16:45:00 -0000 [thread overview]
Message-ID: <20070111164533.GA20499@nevyn.them.org> (raw)
In-Reply-To: <jevejdh69d.fsf@sykes.suse.de>
On Thu, Jan 11, 2007 at 05:34:22PM +0100, Andreas Schwab wrote:
> This is broken. You can't use PC_REGNUM unconditionally without checking
> whether that register actually exists. The ia64 does not have such a
> register.
I assume it causes trouble there. Sorry. Does this help (untested)?
--
Daniel Jacobowitz
CodeSourcery
2007-01-11 Daniel Jacobowitz <dan@codesourcery.com>
* frame.c (get_prev_frame_1): Check PC_REGNUM before using it.
Index: frame.c
===================================================================
RCS file: /cvs/src/src/gdb/frame.c,v
retrieving revision 1.218
diff -u -p -r1.218 frame.c
--- frame.c 9 Jan 2007 20:19:15 -0000 1.218
+++ frame.c 11 Jan 2007 16:44:40 -0000
@@ -1221,10 +1221,17 @@ get_prev_frame_1 (struct frame_info *thi
have different frame IDs, the new frame will be bogus; two
functions can't share a register save slot for the PC. This can
happen when the prologue analyzer finds a stack adjustment, but
- no PC save. This check does assume that the "PC register" is
- roughly a traditional PC, even if the gdbarch_unwind_pc method
- frobs it. */
+ no PC save.
+
+ This check does assume that the "PC register" is roughly a
+ traditional PC, even if the gdbarch_unwind_pc method adjusts
+ it (we do not rely on the value, only on the unwound PC being
+ dependent on this value). A potential improvement would be
+ to have the frame prev_pc method and the gdbarch unwind_pc
+ method set the same lval and location information as
+ frame_register_unwind. */
if (this_frame->level > 0
+ && PC_REGNUM >= 0
&& get_frame_type (this_frame) == NORMAL_FRAME
&& get_frame_type (this_frame->next) == NORMAL_FRAME)
{
next prev parent reply other threads:[~2007-01-11 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 13:58 Daniel Jacobowitz
2006-08-20 16:28 ` Mark Kettenis
2006-08-21 15:58 ` Daniel Jacobowitz
2006-08-22 21:36 ` Mark Kettenis
2006-08-23 9:57 ` Daniel Jacobowitz
2006-11-10 20:16 ` Daniel Jacobowitz
2007-01-11 16:34 ` Andreas Schwab
2007-01-11 16:45 ` Daniel Jacobowitz [this message]
2007-01-11 17:15 ` Andreas Schwab
2007-01-11 17:18 ` Daniel Jacobowitz
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=20070111164533.GA20499@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=schwab@suse.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