Pedro Alves d8d96409c8 Introduce GDB_THREAD_OPTION_EXIT thread option, fix step-over-thread-exit ... When stepping over a breakpoint with displaced stepping, GDB needs to be informed if the stepped thread exits, otherwise the displaced stepping buffer that was allocated to that thread leaks, and this can result in deadlock, with other threads waiting for their turn to displaced step, but their turn never comes. Similarly, when stepping over a breakpoint in line, GDB also needs to be informed if the stepped thread exits, so that is can clear the step over state and re-resume threads. This commit makes it possible for GDB to ask the target to report thread exit events for a given thread, using the new "thread options" mechanism introduced by a previous patch. This only adds the core bits. Following patches in the series will teach the Linux backends (native & gdbserver) to handle the GDB_THREAD_OPTION_EXIT option, and then a later patch will make use of these thread exit events to clean up displaced stepping and inline stepping state properly. Reviewed-By: Andrew Burgess <aburgess@redhat.com> Change-Id: I96b719fdf7fee94709e98bb3a90751d8134f3a38 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27338		2023-11-13 14:16:10 +00:00
..
resume.h
target.c	Introduce GDB_THREAD_OPTION_EXIT thread option, fix step-over-thread-exit	2023-11-13 14:16:10 +00:00
target.h	Introduce GDB_THREAD_OPTION_EXIT thread option, fix step-over-thread-exit	2023-11-13 14:16:10 +00:00
wait.h
waitstatus.c
waitstatus.h