gdb/doc: Remove mention of vCont's default actions
Discussion with qemu folks suggests that the vCont description could be even simpler and clearer. Given we now say: For each inferior thread, the leftmost action with a matching thread-id is applied. There's really no need to even talk about "default" actions, which raises doubts about whether "default" is special in some way (it's not). See <https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg06944.html>. gdb/doc/ChangeLog: 2016-10-29 Pedro Alves <palves@redhat.com> * gdb.texinfo (Packets) <vCont>: Remove mention of default actions.
This commit is contained in:
parent
6bcbbf52b2
commit
39402e6c64
|
@ -1,3 +1,8 @@
|
||||||
|
2016-10-29 Pedro Alves <palves@redhat.com>
|
||||||
|
|
||||||
|
* gdb.texinfo (Packets) <vCont>: Remove mention of default
|
||||||
|
actions.
|
||||||
|
|
||||||
2016-10-26 Pedro Alves <palves@redhat.com>
|
2016-10-26 Pedro Alves <palves@redhat.com>
|
||||||
|
|
||||||
* gdb.texinfo (Packets): Clarify vCont packets with multiple
|
* gdb.texinfo (Packets): Clarify vCont packets with multiple
|
||||||
|
|
|
@ -35538,9 +35538,8 @@ syntax described in @ref{thread-id syntax}. If multiprocess
|
||||||
extensions (@pxref{multiprocess extensions}) are supported, actions
|
extensions (@pxref{multiprocess extensions}) are supported, actions
|
||||||
can be specified to match all threads in a process by using the
|
can be specified to match all threads in a process by using the
|
||||||
@samp{p@var{pid}.-1} form of the @var{thread-id}. An action with no
|
@samp{p@var{pid}.-1} form of the @var{thread-id}. An action with no
|
||||||
@var{thread-id} is called the default action and matches all threads.
|
@var{thread-id} matches all threads. Specifying no actions is an
|
||||||
Specifying multiple default actions is an error; specifying no actions
|
error.
|
||||||
is also an error.
|
|
||||||
|
|
||||||
Currently supported actions are:
|
Currently supported actions are:
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue