Re: [rfa/doc] Add section on interrupts to remote protocol documentation

[Steven Johnson <sjohnson at sakuraindustries dot com>]

I thought that ^C only was relevant after the `C', `c', `S', `s' packets 
and before a Stop Reply Packet.

None of the stubs ive implemented treat "^C" exceptionally, except when 
they are running code.

Otherwise, ^C is ignored as a special character.  What does "interrupt" 
mean when you are not doing anything that can be interrupted?

If you are executing code, then you are in the "Dead space" between the 
packet from GDB to the target to get the target to execute code, and the 
reply from that packet.  I would have thought during this time, and this 
time only ^C has any relevance?  If so then, it doesnt need to be 
quoted, As you cant send a packet during this time.

I think it would be better to say that during this time, and this time 
only is when ^C is relevant, and if received at any other time it is 
processed like that character would be in the message stream.

Steven


Jim Blandy wrote:

> Interesting.  The documentation on the 'X' binary download packet
> doesn't mention C-c as one of the characters that gets quoted.  And,
> in fact, remote.c:remote_write_bytes doesn't quote it.  Who's right
> here?
>
>
>