From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] dummy frames using regcache
Date: Fri, 28 Jun 2002 15:40:00 -0000 [thread overview]
Message-ID: <20020628224058.GA17332@nevyn.them.org> (raw)
In-Reply-To: <3D1CE583.4090801@ges.redhat.com>
On Fri, Jun 28, 2002 at 06:38:59PM -0400, Andrew Cagney wrote:
> >Hello,
> >
> >Attached is the next in the regcache series. This converts dummy frames
> >to the regcache. Tested on the i386.
> >
> >Note the fixme though:
> >
> >+ /* FIXME: cagney/2002-06-26: This should be via the
> >+ gdbarch_register_read() method so that it, on the fly,
> >+ constructs either a raw or pseudo register from the raw
> >+ register cache. */
> >+ regcache_read (registers, regnum, bufferp);
>
> FYI,
>
> >2002-06-26 Andrew Cagney <ac131313@redhat.com>
> >
> > * blockframe.c (generic_find_dummy_frame): Change return type to
> > ``struct regcache''.
> > (struct dummy_frame): Replace field ``registers'' with regcache, a
> > struct regcache object.
> > (generic_find_dummy_frame): Update.
> > (generic_push_dummy_frame): Update. Use regcache_xfree,
> > regcache_xmalloc and regcache_cpy.
> > (generic_pop_dummy_frame): Update. Use regcache_cpy and
> > regcache_xfree.
> > (deprecated_generic_find_dummy_frame): Update.
> > (generic_read_register_dummy): Update. Use
> > regcache_read_as_address.
> > (generic_call_dummy_register_unwind): Update. Use regcache_read.
> >
>
> I've now checked this in (.....holds breath ...).
Great! I'm working on a port where this'll be very helpful.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-06-28 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 13:08 Andrew Cagney
2002-06-28 15:39 ` Andrew Cagney
2002-06-28 15:40 ` 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=20020628224058.GA17332@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb-patches@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