aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPedro Alves <pedro@palves.net>2023-05-18 19:13:45 +0100
committerPedro Alves <pedro@palves.net>2024-05-10 11:25:59 +0100
commit734404845dfd245e26ea900bba84555e8baf09ae (patch)
tree05980e50102cf77e993c08fadaad5dd53964039e
parent8055ea0bb694c37fe3e0a90a17d3b29b85a538c1 (diff)
downloadgdb-734404845dfd245e26ea900bba84555e8baf09ae.zip
gdb-734404845dfd245e26ea900bba84555e8baf09ae.tar.gz
gdb-734404845dfd245e26ea900bba84555e8baf09ae.tar.bz2
Windows gdb: Pending stop and current_event
I noticed that windows_nat_target::get_windows_debug_event does not copy the event recorded in pending stop to windows_process.current_event. This seems like an oversight. The equivalent code in gdbserver/win32-low.cc does copy it. This change will become moot later in the series, but I figure its still clearer to correct the buglet as preparatory patch. Change-Id: Ic8935d854cf67a3a3c4edcbc1a1e8957b800d907
-rw-r--r--gdb/windows-nat.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/gdb/windows-nat.c b/gdb/windows-nat.c
index 2cfc855..2c55ec0 100644
--- a/gdb/windows-nat.c
+++ b/gdb/windows-nat.c
@@ -1556,6 +1556,7 @@ windows_nat_target::get_windows_debug_event
{
thread_id = stop->thread_id;
*ourstatus = stop->status;
+ windows_process.current_event = stop->event;
ptid_t ptid (windows_process.current_event.dwProcessId, thread_id);
windows_thread_info *th = windows_process.find_thread (ptid);