diff options
| author | Pedro Alves <pedro@palves.net> | 2021-01-11 23:11:57 +0000 |
|---|---|---|
| committer | Pedro Alves <pedro@palves.net> | 2021-02-03 01:15:16 +0000 |
| commit | ac7d717c1eb2421d64135ef0e6cf19de74b8d5d3 (patch) | |
| tree | 53a4eeb69008dd409f66134ca0e9af4b72812ee6 /gdb/ChangeLog | |
| parent | e87f0fe82375ffe508da44172fcfe04e258ddc9c (diff) | |
| download | gdb-ac7d717c1eb2421d64135ef0e6cf19de74b8d5d3.zip gdb-ac7d717c1eb2421d64135ef0e6cf19de74b8d5d3.tar.gz gdb-ac7d717c1eb2421d64135ef0e6cf19de74b8d5d3.tar.bz2 | |
detach with in-line step over in progress
A following patch will add a testcase that has a number of threads
constantly stepping over a breakpoint, and then has GDB detach the
process. That testcase exercises both "set displaced-stepping
on/off". Testing with "set displaced-stepping off" reveals that GDB
does not handle the case of the user typing "detach" just while some
thread is in the middle of an in-line step over. If that thread
belongs to the inferior that is being detached, then the step-over
never finishes, and threads of other inferiors are never re-resumed.
This fixes it.
gdb/ChangeLog:
* infrun.c (struct step_over_info): Initialize fields.
(prepare_for_detach): Handle ongoing in-line step over.
Diffstat (limited to 'gdb/ChangeLog')
| -rw-r--r-- | gdb/ChangeLog | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 4113e3a..365d137 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,5 +1,10 @@ 2021-02-03 Pedro Alves <pedro@palves.net> + * infrun.c (struct step_over_info): Initialize fields. + (prepare_for_detach): Handle ongoing in-line step over. + +2021-02-03 Pedro Alves <pedro@palves.net> + * linux-nat.c (linux_nat_target::detach): Remove breakpoints here... * remote.c (remote_target::remote_detach_1): ... and here ... |