compatibility between gdb and stub

[Kevin Buettner]

On Nov 21, 10:44am, Romain Berrendonner wrote:

> On 2002-11-20, Kevin Buettner wrote :
> 
> > 
> > As I understand it, if a stub replies with a short "g" packet, then
> > gdb will simply regard the missing registers as being unavailable.
> > 
> Let's take the example of the 750, with a stub not aware of fpscr.
> 
> They are many registers after fpscr (the first of them is sr0).
> With this scheme, when the stub sends back the answer to a 'g' packet,
> gdb will consider that the content of fpscr is the content of sr0, and that
> thrm3 (the last register) is not available.

This would be true if fpscr was simply added in the middle.  However,
when I "added" fpscr, I made it replace a previously unused slot.  So,
what should happen in this case is that gdb will simply get a zero (or
some other bogus value) for fpscr.

Kevin