This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RFA: GDB manual: note similarity of 'S' and 'T' responses
- From: Jim Blandy <jimb at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Date: Thu, 17 Aug 2006 01:25:24 -0700
- Subject: RFA: GDB manual: note similarity of 'S' and 'T' responses
2006-08-17 Jim Blandy <jimb@codesourcery.com>
* gdb.texinfo (Stop Reply Packets): Note similarity of 'S' and 'T'
responses.
Index: gdb/doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.348
diff -u -r1.348 gdb.texinfo
--- gdb/doc/gdb.texinfo 8 Aug 2006 22:18:22 -0000 1.348
+++ gdb/doc/gdb.texinfo 17 Aug 2006 08:23:46 -0000
@@ -23293,14 +23293,17 @@
@item S @var{AA}
The program received signal number @var{AA} (a two-digit hexidecimal
-number).
+number). This is equivalent to a @samp{T} response with no
+@var{n}:@var{r} pairs.
@item T @var{AA} @var{n1}:@var{r1};@var{n2}:@var{r2};@dots{}
@cindex @samp{T} packet reply
The program received signal number @var{AA} (a two-digit hexidecimal
-number). Single-step and breakpoint traps are reported this way. The
-@samp{@var{n}:@var{r}} pairs give the values of important registers or
-other information:
+number). This is equivalent to an @samp{S} response, except that the
+@samp{@var{n}:@var{r}} pairs can carry values of important registers
+and other information directly in the stop reply packet, reducing
+round-trip latency. Single-step and breakpoint traps are reported
+this way. Each @samp{@var{n}:@var{r}} pair is interpreted as follows:
@enumerate
@item
If @var{n} is a hexidecimal number, it is a register number, and the