This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: The REG_NUM and REGISTER_BYTES problem


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]