Buy the book!
|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
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 = two hex digit signal number; n... = register number
(hex), r... = target byte ordered register contents, size defined
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 protocol.
The process exited, and AA is the exit status. This is only applicable to certain targets.
The process terminated with signal AA.
AA = signal number; t... = address of symbol
_start; d... = base of data section; b... =
base of bss section. Note: only used by Cisco Systems targets.
The difference between this reply and the `qOffsets' query is that
the `N' packet may arrive spontaneously whereas the `qOffsets'
is a query initiated by the host debugger.
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.
|webmaster||delorie software privacy|
|Copyright © 2003 by The Free Software Foundation||Updated Jun 2003|