diff options
| author | Pedro Alves <pedro@palves.net> | 2022-12-05 20:44:39 +0000 |
|---|---|---|
| committer | Pedro Alves <pedro@palves.net> | 2023-11-13 14:16:10 +0000 |
| commit | 7730e5c6c2658658a032a957a78e663350dc5124 (patch) | |
| tree | 3437b23810e853b676cbc8c5b3dfc01a1ce49858 /gdb/testsuite/gdb.python | |
| parent | ad320fbf91e6808699cb69cccca7299a2332074d (diff) | |
| download | binutils-7730e5c6c2658658a032a957a78e663350dc5124.zip binutils-7730e5c6c2658658a032a957a78e663350dc5124.tar.gz binutils-7730e5c6c2658658a032a957a78e663350dc5124.tar.bz2 | |
Move deleting thread on TARGET_WAITKIND_THREAD_EXITED to core
Currently, infrun assumes that when TARGET_WAITKIND_THREAD_EXITED is
reported, the corresponding GDB thread has already been removed from
the GDB thread list.
Later in the series, that will no longer work, as infrun will need to
refer to the thread's thread_info when it processes
TARGET_WAITKIND_THREAD_EXITED.
As preparation, this patch makes deleting the GDB thread
responsibility of infrun, instead of the target.
Reviewed-By: Andrew Burgess <aburgess@redhat.com>
Change-Id: I013d87f61ffc9aaca49f0d6ce2a43e3ea69274de
Diffstat (limited to 'gdb/testsuite/gdb.python')
0 files changed, 0 insertions, 0 deletions