From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: The REG_NUM and REGISTER_BYTES problem
Date: Sun, 02 Dec 2001 15:02:00 -0000 [thread overview]
Message-ID: <20011202180304.A7998@nevyn.them.org> (raw)
In-Reply-To: <3C084D16.4090205@cygnus.com>
On Fri, Nov 30, 2001 at 10:23:02PM -0500, Andrew Cagney wrote:
> To address this, I intend changing regcache and remote.c so that they
> treat all registers equal (don't differentiate between real and psuedo
> registers). Instead, regchace reserves space for all of them, and
> remote.c will fetch any of them when so asked. Exactly what to do with
> all that potential regcache space being the responsibility of the target
> architecture.
>
> By doing this, the immdiate restriction of not being able to expand the
> number of registers is lifted. While some of REGISTER_BYTES and
> NUM_REGS special effects will remain, they won't be causing GDB's
> ability to handle large register sets.
>
> Thoughts?
Well, how will this affect pseudo registers that we can provide but
that the remote stub can not? I'm pretty sure there are some. Is the
intent that such registers "should not" be fetched?
On the subject of the remote protocol, both you and I posted scripts to
generate a register packet description from a text file. What're your
thoughts on adding one of those?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-12-02 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-30 19:23 Andrew Cagney
2001-11-25 12:44 ` Andrew Cagney
2001-12-02 15:02 ` Daniel Jacobowitz [this message]
2001-12-02 21:22 ` 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=20011202180304.A7998@nevyn.them.org \
--to=drow@mvista.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