* gdb.texinfo (Stop Reply Packets): Note similarity of 'S' and 'T'

responses.

gdb/doc/ChangeLog

@@ -1,3 +1,8 @@
+2006-08-17  Jim Blandy  <jimb@codesourcery.com>
+
+	* gdb.texinfo (Stop Reply Packets): Note similarity of 'S' and 'T'
+	responses.
+
 2006-08-08  Joel Brobecker  <brobecker@adacore.com>
 
 	* gdb.texinfo (Source Path): Add documentation for new

gdb/doc/gdb.texinfo

@@ -23293,14 +23293,17 @@ components.
 
 @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
+number).  This is equivalent to an @samp{S} response, except that the
-@samp{@var{n}:@var{r}} pairs give the values of important registers or
+@samp{@var{n}:@var{r}} pairs can carry values of important registers
-other information:
+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