This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
remote ack to [CcSs]
- To: GDB Discussion <gdb at sources dot redhat dot com>,"J. T. Conklin" <jtc at redback dot com>
- Subject: remote ack to [CcSs]
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Wed, 09 May 2001 18:26:53 -0400
J.T.
From remote.c:
/* The s/S/c/C packets do not return status. So if the target does
not support the S or C packets, the debug agent returns an empty
string which is detected in remote_wait(). This protocol defect
is fixed in the e/E packets. */
Thinking about it, I don't think there is anything actually wrong with
this behavour and I'm wondering if the [Ee] packet should have adopted
the same behavour as the [CcSs].
Consider what happens if the code is strictly event driven. Regardless
of which of the [SsCc] or [Ee] packets is used, the code will need to
return to the event-loop and then wait for a response. It would then be
left to remote_wait() to analyze the response and compare it agains the
current target state. If remote_wait() got "" after remote_resume()
issued a [Ee] then remote_wait() (and not remote_resume()) would try
[SsEc] resuming the target by other means and finally returning
non-event to WFI.
Andrew