This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: The REG_NUM and REGISTER_BYTES problem
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: gdb at sources dot redhat dot com
- Date: Sun, 2 Dec 2001 18:03:04 -0500
- Subject: Re: The REG_NUM and REGISTER_BYTES problem
- References: <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