From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] fix popping of dummy frame if inferior gets signal with unwindonsignal
Date: Tue, 18 Nov 2008 12:59:00 -0000 [thread overview]
Message-ID: <20081117233452.GA6909@caradoc.them.org> (raw)
In-Reply-To: <e394668d0811171437u1aaa7682u3dae8708b6b28cf7@mail.gmail.com>
On Mon, Nov 17, 2008 at 02:37:10PM -0800, Doug Evans wrote:
> On Mon, Nov 17, 2008 at 12:42 PM, Ulrich Weigand <uweigand@de.ibm.com> wrote:
> > Daniel Jacobowitz wrote:
> >> On Mon, Nov 17, 2008 at 08:50:13PM +0100, Ulrich Weigand wrote:
> >> > I'm not sure what the point is of having two copies of the regcache
> >> > preserved across the full extent of the inferior call ...
> >>
> >> Maybe in case we get to somewhere we can not backtrace from?
> >
> > OK, good point. The inf_status will always work ...
>
> I don't understand why two copies are needed.
> Can either of you elaborate?
Hypothetically, if you call a function which completely trashes the
registers but not the previous stack, we might not be able to find the
dummy frame to pop. So having it saved somewhere else seems
reasonable. I don't know how to structure that in a useful
least-surprising way though...
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-11-17 23:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 8:28 Doug Evans
2008-11-17 20:02 ` Michael Snyder
2008-11-18 0:00 ` Ulrich Weigand
2008-11-18 1:32 ` Daniel Jacobowitz
2008-11-18 2:19 ` Ulrich Weigand
2008-11-18 5:46 ` Doug Evans
2008-11-18 12:59 ` 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=20081117233452.GA6909@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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