gdb.info: Stop Reply Packets
Go forward to General Query Packets
Go backward to Packets
Go up to Remote Protocol
Go to the top op gdb
Stop Reply Packets
The `C', `c', `S', `s' and `?' packets can receive any of the below as
a reply. In the case of the `C', `c', `S' and `s' packets, that reply
is only returned when the target halts. In the below the exact meaning
of `signal number' is poorly defined. In general one of the UNIX
signal numbering conventions is used.
AA is the signal number
AA = two hex digit signal number; N... = register number (hex),
R... = target byte ordered register contents, size defined by
`DEPRECATED_REGISTER_RAW_SIZE'; N... = `thread', R... = thread
process ID, this is a hex integer; N... = (`watch' | `rwatch' |
`awatch', R... = data address, this is a hex integer; N... = other
string not starting with valid hex digit. GDB should ignore this
N..., R... pair and go on to the next. This way we can extend the
The process exited, and AA is the exit status. This is only
applicable to certain targets.
The process terminated with signal AA.
XX... is hex encoding of ASCII data. This can happen at any time
while the program is running and the debugger should continue to
wait for `W', `T', etc.
CALL-ID is the identifier which says which host system call should
be called. This is just the name of the function. Translation
into the correct system call is only applicable as it's defined in
GDB. *Note File-I/O remote protocol extension::, for a list of
implemented system calls.
PARAMETER... is a list of parameters as defined for this very
The target replies with this packet when it expects GDB to call a
host system call on behalf of the target. GDB replies with an
appropriate `F' packet and keeps up waiting for the next reply
packet from the target. The latest `C', `c', `S' or `s' action is
expected to be continued. *Note File-I/O remote protocol
extension::, for more details.
Created Mon Nov 8 17:42:41 2004 on tillpc with info_to_html version 0.9.6.