public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH] Mask x86 segment registers in Windows gdbserver
Date: Tue, 19 Dec 2023 07:48:23 -0700	[thread overview]
Message-ID: <20231219144823.1070597-1-tromey@adacore.com> (raw)

A test internal to AdaCore prints the segment registers.  When run
using gdbserver, it shows:

    (gdb) print /x $gs
    $6 = 0x2b0000

However, the segment registers are only 16 bits -- so this has some
invalid bits.

gdb's windows-nat.c has long had a fix for this problem.  This patch
applies the fix to gdbserver as well.
---
 gdbserver/win32-i386-low.cc | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/gdbserver/win32-i386-low.cc b/gdbserver/win32-i386-low.cc
index f78e0120678..d60ff83c15d 100644
--- a/gdbserver/win32-i386-low.cc
+++ b/gdbserver/win32-i386-low.cc
@@ -35,6 +35,12 @@ using namespace windows_nat;
 #define FCS_REGNUM 27
 #define FOP_REGNUM 31
 
+#define I386_CS_REGNUM 10
+#define I386_GS_REGNUM 15
+
+#define AMD64_CS_REGNUM 18
+#define AMD64_GS_REGNUM 23
+
 #define FLAG_TRACE_BIT 0x100
 
 static struct x86_debug_reg_state debug_reg_state;
@@ -459,6 +465,18 @@ static const int amd64_mappings[] =
 
 #endif /* __x86_64__ */
 
+/* Return true if R is a segment register.  */
+static bool
+is_segment_register (int r)
+{
+#ifdef __x86_64__
+  if (!windows_process.wow64_process)
+    return r >= AMD64_CS_REGNUM && r <= AMD64_GS_REGNUM;
+  else
+#endif
+    return r >= I386_CS_REGNUM && r <= I386_GS_REGNUM;
+}
+
 /* Fetch register from gdbserver regcache data.  */
 static void
 i386_fetch_inferior_register (struct regcache *regcache,
@@ -491,6 +509,14 @@ i386_fetch_inferior_register (struct regcache *regcache,
       l = (*((long *) context_offset) >> 16) & ((1 << 11) - 1);
       supply_register (regcache, r, (char *) &l);
     }
+  else if (is_segment_register (r))
+    {
+      /* GDB treats segment registers as 32bit registers, but they are
+	 in fact only 16 bits long.  Make sure we do not read extra
+	 bits from our source buffer.  */
+      l = *((long *) context_offset) & 0xffff;
+      supply_register (regcache, r, (char *) &l);
+    }
   else
     supply_register (regcache, r, context_offset);
 }
-- 
2.43.0


             reply	other threads:[~2023-12-19 14:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 14:48 Tom Tromey [this message]
2023-12-20 22:03 ` John Baldwin
2023-12-21 20:29   ` Tom Tromey
2024-01-18 18:51     ` Tom Tromey
2024-01-22 16:57       ` John Baldwin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231219144823.1070597-1-tromey@adacore.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).