aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2021-05-03 08:57:46 -0600
committerTom Tromey <tromey@adacore.com>2021-05-03 12:40:19 -0600
commit8228833924fa3c92a436a5f938a94dae180773f9 (patch)
treef5989b5a31d5d890080ea977d3531ab6ba8d5583
parentf08708cbf59ec153eac33d7a2a99ef99f1ca825a (diff)
downloadgdb-8228833924fa3c92a436a5f938a94dae180773f9.zip
gdb-8228833924fa3c92a436a5f938a94dae180773f9.tar.gz
gdb-8228833924fa3c92a436a5f938a94dae180773f9.tar.bz2
Fix x86_64 mingw build
PR build/27807 points out that my recent changes to the Windows port missed a spot in win32-i386-low.cc -- a call to win32_Wow64GetThreadContext remained, causing link errors in gdbserver. This happened because I tested an i686 build, but this code is only used on an x86_64 build. This patch fixes the bug. I am checking it in. gdbserver/ChangeLog 2021-05-03 Tom Tromey <tromey@adacore.com> PR build/27807: * win32-i386-low.cc (i386_get_thread_context): Call Wow64GetThreadContext, not win32_Wow64GetThreadContext.
-rw-r--r--gdbserver/ChangeLog6
-rw-r--r--gdbserver/win32-i386-low.cc2
2 files changed, 7 insertions, 1 deletions
diff --git a/gdbserver/ChangeLog b/gdbserver/ChangeLog
index 057ed15..8ff59d1 100644
--- a/gdbserver/ChangeLog
+++ b/gdbserver/ChangeLog
@@ -1,3 +1,9 @@
+2021-05-03 Tom Tromey <tromey@adacore.com>
+
+ PR build/27807:
+ * win32-i386-low.cc (i386_get_thread_context): Call
+ Wow64GetThreadContext, not win32_Wow64GetThreadContext.
+
2021-04-30 Tom Tromey <tromey@adacore.com>
* win32-low.cc (do_initial_child_stuff): Update.
diff --git a/gdbserver/win32-i386-low.cc b/gdbserver/win32-i386-low.cc
index 5fc4be0..e2afd2a 100644
--- a/gdbserver/win32-i386-low.cc
+++ b/gdbserver/win32-i386-low.cc
@@ -260,7 +260,7 @@ i386_get_thread_context (windows_thread_info *th)
BOOL ret;
#ifdef __x86_64__
if (wow64_process)
- ret = win32_Wow64GetThreadContext (th->h, &th->wow64_context);
+ ret = Wow64GetThreadContext (th->h, &th->wow64_context);
else
#endif
ret = GetThreadContext (th->h, &th->context);