Re: remote ack to [CcSs]

[Andrew Cagney <ac131313 at cygnus dot com>]

> Andrew> From remote.c:
> Andrew>
> Andrew> /* The s/S/c/C packets do not return status.  So if the target does
> Andrew> not support the S or C packets, the debug agent returns an empty
> Andrew> string which is detected in remote_wait().  This protocol defect
> Andrew> is fixed in the e/E packets. */
> Andrew>
> Andrew> Thinking about it, I don't think there is anything actually wrong with
> Andrew> this behavour and I'm wondering if the [Ee] packet should have adopted
> Andrew> the same behavour as the [CcSs].
> 
> Well I'm still convinced that the fallback from S/C to s/c is a botch.
> It requires global variables "last_sent_signal" and "last_sent_step"
> to communicate state between remote_resume() and remote_wait() so that
> remote_wait() can pick up the pieces when remote_resume() didn't do
> it's job.  Doing the same for the step-over-range command would require 
> even more global state.


True, the thing is that, if remote.c ever gets fully inverted it is 
going to need that global state any way :-/

	enjoy,
		Andrew