From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Don't overshoot when executing cfa instructions
Date: Sat, 27 Jun 2009 22:33:00 -0000 [thread overview]
Message-ID: <20090627223341.GB14420@caradoc.them.org> (raw)
In-Reply-To: <m2ws6xqptl.fsf@igel.home>
On Sun, Jun 28, 2009 at 12:23:02AM +0200, Andreas Schwab wrote:
> The dwarf2 unwinder is careful to substract one from pc when finding the
> associated fde, but when executing the cfa instructions it uses the
> original pc as the limit, which may cause it to execute too much, for
> example if this is a frame calling a noreturn function. Tested on
> powerpc-linux.
Actually, before approving this I have a question. What about state
changes caused by the branch?
I remember a similar problem with location lists. Before the branch,
a variable lives at some location. Inside the called function, it is
gone. Did we ever find a representation for that? Does it rely
on the instruction after the branch marking the register as clobbered?
Sorry, I can't find a link.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-06-27 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 22:23 Andreas Schwab
2009-06-27 22:28 ` Daniel Jacobowitz
2009-06-27 22:33 ` Daniel Jacobowitz [this message]
2009-06-29 13:19 ` Andreas Schwab
2009-06-29 14:33 ` 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=20090627223341.GB14420@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.org \
/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