diff options
| author | Pedro Alves <palves@redhat.com> | 2016-10-26 11:08:27 +0100 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2016-10-26 16:22:05 +0100 |
| commit | ca6eff59089ff1a1772ac95d4890f94b3eef2796 (patch) | |
| tree | 4f756dc01f03d45f6be0a623903e1c0523e8981b /gdb/target-delegates.c | |
| parent | ef4a339527a41802fbab70af25d6e4788f35dcc8 (diff) | |
| download | binutils-ca6eff59089ff1a1772ac95d4890f94b3eef2796.zip binutils-ca6eff59089ff1a1772ac95d4890f94b3eef2796.tar.gz binutils-ca6eff59089ff1a1772ac95d4890f94b3eef2796.tar.bz2 | |
gdb/doc: Clarify vCont packet description
Specifically, what happens with multiple actions that could match a
thread, and what happens when we get a vCont action that matches a
thread that was already running. E.g., what does:
"vCont;s:2"
"vCont;s:1;c"
mean for thread 2.
(Thread 2 continues stepping.)
gdb/doc/ChangeLog:
2016-10-26 Pedro Alves <palves@redhat.com>
* gdb.texinfo (Packets): Clarify vCont packets with multiple
actions that match a thread, and what happens when an action
matches a thread that is already running.
Diffstat (limited to 'gdb/target-delegates.c')
0 files changed, 0 insertions, 0 deletions