diff options
| author | Pedro Alves <palves@redhat.com> | 2015-11-30 16:05:14 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2015-11-30 18:36:41 +0000 |
| commit | 066f6b6edcb63b363cc9a95c3727b996d1895549 (patch) | |
| tree | 0f3d16c8554b188120b7134f91511d40dfea33d4 /gdb/ChangeLog | |
| parent | 6efcd9a8b3dc6a01cd1f212a2d854e5f8896715e (diff) | |
| download | gdb-066f6b6edcb63b363cc9a95c3727b996d1895549.zip gdb-066f6b6edcb63b363cc9a95c3727b996d1895549.tar.gz gdb-066f6b6edcb63b363cc9a95c3727b996d1895549.tar.bz2 | |
attach + target always in non-stop mode: stop all threads
When running with "maint set target-non-stop on", and in all-stop
mode, nothing is stopping all threads after attaching. vAttach in
non-stop can leave all threads running and GDB has to explicitly pause
them.
This is not visible with the native target, as in that case, attach
always stops all threads (the core re-resumes them in case of
"attach&").
In addition, it's not defined which thread manages to report the
initial attach stop, so always pick the lowest one (otherwise
multi-attach.exp regresses).
gdb/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
* infcmd.c (attach_post_wait): If the target is always in non-stop
mode, and the UI is in all-stop mode, stop all threads and pick
the one with lowest number as current.
Diffstat (limited to 'gdb/ChangeLog')
| -rw-r--r-- | gdb/ChangeLog | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 6833076..3e10e2b 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,11 @@ 2015-11-30 Pedro Alves <palves@redhat.com> + * infcmd.c (attach_post_wait): If the target is always in non-stop + mode, and the UI is in all-stop mode, stop all threads and pick + the one with lowest number as current. + +2015-11-30 Pedro Alves <palves@redhat.com> + * gdbthread.h (switch_to_thread_no_regs): Declare. * infcmd.c (setup_inferior): New function, factored out from ... (attach_command_post_wait): ... this. Rename to ... |