This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Drop documentation of unimplemented vCont;T packet.
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Date: Sun, 4 Oct 2009 16:06:25 +0100
- Subject: Drop documentation of unimplemented vCont;T packet.
I'd like to drop the mention of the vCont;T packet from the remote
protocol documentation. It was added as part of documentation of
the non-stop remote protocol extensions, but was never actually
needed or implemented.
Okay, for head and branch?
--
Pedro Alves
2009-10-04 Pedro Alves <pedro@codesourcery.com>
* gdb.texinfo (Remote Protocol): Don't mention vCont;T.
---
gdb/doc/gdb.texinfo | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
Index: src/gdb/doc/gdb.texinfo
===================================================================
--- src.orig/gdb/doc/gdb.texinfo 2009-10-04 15:57:02.000000000 +0100
+++ src/gdb/doc/gdb.texinfo 2009-10-04 15:57:59.000000000 +0100
@@ -28220,16 +28220,14 @@ Step.
Step with signal @var{sig}. The signal @var{sig} should be two hex digits.
@item t
Stop.
-@item T @var{sig}
-Stop with signal @var{sig}. The signal @var{sig} should be two hex digits.
@end table
The optional argument @var{addr} normally associated with the
@samp{c}, @samp{C}, @samp{s}, and @samp{S} packets is
not supported in @samp{vCont}.
-The @samp{t} and @samp{T} actions are only relevant in non-stop mode
-(@pxref{Remote Non-Stop}) and may be ignored by the stub otherwise.
+The @samp{t} action is only relevant in non-stop mode
+(@pxref{Remote Non-Stop}) and may be ignored by the stub otherwise.
A stop reply should be generated for any affected thread not already stopped.
When a thread is stopped by means of a @samp{t} action,
the corresponding stop reply should indicate that the thread has stopped with