Re: Interrupting remote targets from GDB

[Eli Zaretskii <eliz at gnu dot org>]

> Date: Thu, 17 Nov 2005 11:20:43 -0700
> From: Kevin Buettner <kevinb@redhat.com>
> 
> I think this documentation is fine, but would also like to see some
> suitable documentation added to the section describing the GDB remote
> protocol.  I suggest that a section called "Interrupts" be added in
> between the sections "Register Packet Format" and "Examples".  I propose
> that it contain the following text:
> 
>     When a program on the remote target is running, GDB may attempt
>     to interrupt it by sending a `Ctrl-C' or a BREAK, control of which
>     is specified via GDB's `remotebreak' setting.  The precise meaning
>     of BREAK is defined by the transport mechanism and may, in fact,
>     be undefined.  `Ctrl-C', on the other hand, is defined for all
>     transport mechanisms and is represented by sending the single byte
>     0x03.  `Ctrl-C' must not be sent as part of a packet as defined in
>     the "Overview".
>     
>     Stubs are not required to recognize these interrupt mechanisms and
>     the precise meaning associated with receipt of the interrupt is
>     implementation defined.  If the stub is successful at interrupting
>     the running program, it is expected that it will send one of the
>     `Stop Reply Packets' to GDB as a result of successfully stopping
>     the program.
> 
> Comments?

Fine with me.  Can you craft a patch and post it on gdb-patches for
review?