From: Andrew Cagney <ac131313@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>, cagney@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: Unwinding dummy frames on the i386
Date: Fri, 07 Mar 2003 22:13:00 -0000 [thread overview]
Message-ID: <3E691984.4030207@redhat.com> (raw)
In-Reply-To: <200303072059.h27KxgX1029877@elgar.kettenis.dyndns.org>
> For now I've worked around this by having my own do-nothing
> i386_save_dummy_frame_tos(), and having i386_unwind_dummy_id() return
> contents of the (saved) frame pointer register for the frame's base.
> Is there a better way to solve this?
Can i386_save_dummy_frame_tos() save the `frame pointer register' that
the unwind_dummy_id() method later returns?
While the TOS in save_dummy_frame_tos() might have once stood for
top-of-stack, there isn't anything saying that it has to be the stack
top. A better name for tha functioin's successor would be
save_dummy_frame_id()
Andrew
next prev parent reply other threads:[~2003-03-07 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 20:59 Mark Kettenis
2003-03-07 22:13 ` Andrew Cagney [this message]
2003-03-08 11:42 ` Mark Kettenis
2003-03-08 15:20 ` Andrew Cagney
2003-03-08 17:32 ` Mark Kettenis
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=3E691984.4030207@redhat.com \
--to=ac131313@redhat.com \
--cc=cagney@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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