aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc
diff options
context:
space:
mode:
authorPedro Alves <palves@redhat.com>2013-11-14 19:43:27 +0000
committerPedro Alves <palves@redhat.com>2013-11-14 19:52:21 +0000
commit36fa80421a9edbf97fc6081557509937bc717bc1 (patch)
treedbaf2fc4b13188d34ce98aa3e65e0b8ce67c0023 /gdb/doc
parent4f5d7f635cd1dd81575edb35395272ee3d535502 (diff)
downloadgdb-36fa80421a9edbf97fc6081557509937bc717bc1.zip
gdb-36fa80421a9edbf97fc6081557509937bc717bc1.tar.gz
gdb-36fa80421a9edbf97fc6081557509937bc717bc1.tar.bz2
infrun.c:handle_signal_stop: Move initial connection/attachment handling code earlier.
Before all this stop_soon handling, we have code that can end in keep_going. Particularly, the thread_hop_needed code looked suspicious considering breakpoint always-inserted mode, though on closer inspection, it'd take connecting to multiple remote targets that shared the same address space to trigger that. Still, I think it's clearer if all this remote connection setup / attach code is placed early, before any keep_going path could be reached. gdb/ 2013-11-14 Pedro Alves <palves@redhat.com> * infrun.c (handle_signal_stop): Move STOP_QUIETLY, STOP_QUIETLY_REMOTE and 'stop_after_trap' handling earlier.
Diffstat (limited to 'gdb/doc')
0 files changed, 0 insertions, 0 deletions