From: Andrew Cagney <ac131313@redhat.com>
To: gdb@sources.redhat.com
Subject: RFC: dummy.[hc] and ``struct dummy''
Date: Thu, 26 Sep 2002 15:47:00 -0000 [thread overview]
Message-ID: <3D938E6F.6090809@redhat.com> (raw)
Hello,
I'd like to float the idea of moving all the generic dummy frame code
into a new file dummy.[hc].
Things like hand_function_call() would then use a ``struct dummy'' that
contains the information for the dummy frame currently being
constructed. That way the current global top-of-dummy stack assumption
is removed.
This should also make it simplier/easier to do things like make what is
currently a single global dummy frame stack part of the ``thread_info''
object. (Figuring out why one would want to do this is left as an
exercise for the reader. LiamS, GraceS and I stumbled across this
think-o :-).
Andrew
next reply other threads:[~2002-09-26 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 15:47 Andrew Cagney [this message]
2002-09-27 10:12 ` Eli Zaretskii
2002-09-27 11:20 ` Andrew Cagney
2002-09-27 11:21 ` Daniel Jacobowitz
2002-09-27 11:38 ` Elena Zannoni
2002-09-27 11:59 ` Kevin Buettner
2002-09-27 12:07 ` Andrew Cagney
2002-09-27 12:15 ` Elena Zannoni
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=3D938E6F.6090809@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