attach + target always in non-stop mode: stop all threads
authorPedro Alves <palves@redhat.com>
Mon, 30 Nov 2015 16:05:14 +0000 (16:05 +0000)
committerPedro Alves <palves@redhat.com>
Mon, 30 Nov 2015 18:36:41 +0000 (18:36 +0000)
commit066f6b6edcb63b363cc9a95c3727b996d1895549
tree0f3d16c8554b188120b7134f91511d40dfea33d4
parent6efcd9a8b3dc6a01cd1f212a2d854e5f8896715e
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.
gdb/ChangeLog
gdb/infcmd.c
This page took 0.025013 seconds and 4 git commands to generate.