From 08a0efd07a826b0630fa15cb07241558d184582c Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Sun, 4 Oct 2009 17:37:57 +0000 Subject: [PATCH] * gdb.texinfo (Remote Protocol): Don't mention vCont;T. --- gdb/doc/ChangeLog | 4 ++++ gdb/doc/gdb.texinfo | 6 ++---- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 4b20f53..12cd7e5 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,7 @@ +2009-10-04 Pedro Alves + + * gdb.texinfo (Remote Protocol): Don't mention vCont;T. + 2009-09-26 Pierre Muller * gdb.texinfo (Cygwin Native): Mention support for Ctrl-BREAK. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 07b325d..a659b65 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -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 -- 2.7.4