This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: read_register_byte can't work with pseudo-reg model
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Cc: Richard dot Earnshaw at arm dot com, Elena Zannoni <ezannoni at redhat dot com>, gdb at sources dot redhat dot com
- Date: Fri, 17 May 2002 15:50:36 +0100
- Subject: Re: read_register_byte can't work with pseudo-reg model
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
rearnsha@arm.com said:
> Would the following tweak be acceptable? That is, only do the update
> if the register has a name.
> else if (REGISTER_NAME (regnum) != NULL && *REGISTER_NAME (regnum)
> != '\0')
> {
> /* Is this register completely within the range the user is
> writing? */
> if (myregstart <= regstart && regend <= myregend)
> write_register_gen (regnum, myaddr + (regstart - myregstart));
> /* The register partially overlaps the range being written. */
> else
> {
I've just noticed that read_register_bytes is doing almost exactly this.
Why do the two differ?
R.