Re: parcelling up struct gdbarch

Andrew Cagney
2001-07-19T07:51:00Z

>
> And it works. I currently move handling of the 'g' and 'G' packets off
> into the low-* file, which makes drastically more sense anyway. The
> code for prepare_resume_reply still needs to be handled, but the
> changes are trivial once the rest is in place.

I'm sure it will work.

> In remote.c, I add a 'qRegisters' packet with the reply
> 'qRegisters:IDENTIFIER', where IDENTIFIER is a (hex-encoded) defined
> name. It defines a register numbering, which remote.c takes care to
> use when talking to the target if one is available. The client-side
> changes are finished and I'll post them in the morning when I'm awake
> enough to write a proper changelog.

Just a heads up. This ``IDENTIFIER'' has consequences. The mechanics
are the easy bit. It is sorting out things like how to consitently
define ``IDENTIFER'' that isn't.

Andrew