From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com
Subject: Re: Identifying a dummy frame using a frame id
Date: Wed, 26 Feb 2003 01:28:00 -0000 [thread overview]
Message-ID: <3E5C18BE.30801@redhat.com> (raw)
In-Reply-To: <200302260120.h1Q1K6g15139@duracef.shout.net>
>> Now, there is a little detail missing - how GDB relocate the dummy frame
>> object that contains those saved registers. The problem is that GDB
>> can't just take the most recent one as, due to long jumps and the like,
>> it can be wrong.
>
>
> I can't comment on the internal mechanism, but I know that as a user of
> gdb, if something happens during a hand function call to marker2() like
> gdb hitting another breakpoint or me hitting ^C, then gdb starts acting
> a little drunk at that point. So I bet that explicit save/restore of
> these frames would help.
FYI, that's a different problem.
This proposal just refines the mechanism used to identify a dummy frame.
For something like the i386, there would be no immediate change in
behavior.
Andrew
next prev parent reply other threads:[~2003-02-26 1:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 1:20 Michael Elizabeth Chastain
2003-02-26 1:28 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-26 1:13 Andrew Cagney
2003-02-26 1:44 ` Andrew Cagney
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=3E5C18BE.30801@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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