From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Identifying a dummy frame using a frame id
Date: Wed, 26 Feb 2003 01:44:00 -0000 [thread overview]
Message-ID: <3E5C1C9E.8030401@redhat.com> (raw)
In-Reply-To: <3E5C1532.4030801@redhat.com>
> - get_dummy_frame_id (target registers)
> Given a target stopped on that dummy frame breakpoint, return a frame ID that exactly matches dummy_frame_id() above.
Refinement #1.
unwind dummy frame id (next_frame)
Given the `next' frame, use frame_register_unwind() to construct the
dummy frame's ID.
Why? Because this also needs to work when the dummy-frame isn't
innermost (the inner most frame edge case is covered by passing it the
sentinel frame).
(my brain hurts!)
Andrew
next prev parent reply other threads:[~2003-02-26 1:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 1:13 Andrew Cagney
2003-02-26 1:44 ` Andrew Cagney [this message]
2003-02-26 1:20 Michael Elizabeth Chastain
2003-02-26 1:28 ` 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=3E5C1C9E.8030401@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.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