mirrors/binutils-gdb
0
0
Fork 0
mirror of https://sourceware.org/git/binutils-gdb.git synced 2025-01-23 00:13:53 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

* gdb.texinfo (Remote Protocol): Don't mention vCont;T.

Browse Source
This commit is contained in:
Pedro Alves 2009-10-04 17:37:57 +00:00
parent d166c213e0
commit 08a0efd07a
2 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/doc/ChangeLog
View File

@ -1,3 +1,7 @@
2009-10-04 Pedro Alves <pedro@codesourcery.com>
* gdb.texinfo (Remote Protocol): Don't mention vCont;T.
2009-09-26 Pierre Muller <muller@ics.u-strasbg.fr>
* gdb.texinfo (Cygwin Native): Mention support for Ctrl-BREAK.

6
gdb/doc/gdb.texinfo
View File

@ -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