From: Pedro Alves <pedro@palves.net>
Date: Thu, 18 May 2023 18:13:45 +0000 (+0100)
Subject: Windows gdb: Pending stop and current_event
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a23cf2fe9db5f54e41e9edca2664e02e769e4a02;p=thirdparty%2Fbinutils-gdb.git

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.

Approved-By: Tom Tromey <tom@tromey.com>
Change-Id: Ic8935d854cf67a3a3c4edcbc1a1e8957b800d907
---

diff --git a/gdb/windows-nat.c b/gdb/windows-nat.c
index f954048dffe..9b3f86de914 100644
--- a/gdb/windows-nat.c
+++ b/gdb/windows-nat.c
@@ -1456,6 +1456,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);