diff options
author | John Baldwin <jhb@FreeBSD.org> | 2023-08-14 13:38:42 -0700 |
---|---|---|
committer | John Baldwin <jhb@FreeBSD.org> | 2023-08-14 13:38:42 -0700 |
commit | a6f51542941e072d942fc8df7353bd10097974ea (patch) | |
tree | 7b9db7827471e8102be2a72e372942600ac9dedc /gdb/testsuite/gdb.python | |
parent | 1b0fa45741276182cbb42d8a78b5eba0150d47a1 (diff) | |
download | binutils-a6f51542941e072d942fc8df7353bd10097974ea.zip binutils-a6f51542941e072d942fc8df7353bd10097974ea.tar.gz binutils-a6f51542941e072d942fc8df7353bd10097974ea.tar.bz2 |
fbsd-nat: Defer any ineligible events reported by wait.
If wait_1 finds an event for a thread or process that does not match
the set of threads and processes previously resumed, defer the event.
If the event is for a specific thread, suspend the thread and continue
the associated process before waiting for another event.
One specific example of such an event is if a thread is created while
another thread in the same process hits a breakpoint. If the second
thread's event is reported first, the target resume method does not
yet "know" about the new thread and will not suspend it via
PT_SUSPEND. When wait is called, it will probably return the event
from the first thread before the result of the step from second
thread. This is the case reported in PR 21497.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=21497
Diffstat (limited to 'gdb/testsuite/gdb.python')
0 files changed, 0 insertions, 0 deletions