From: Hannes Domani <ssbssa@yahoo.de>
To: gdb-patches@sourceware.org
Subject: [PATCH] Windows gdb: Fix resetting of the debug-registers bit in ContextFlags
Date: Sat, 27 Jun 2026 16:27:40 +0200 [thread overview]
Message-ID: <20260627142740.3995235-1-ssbssa@yahoo.de> (raw)
In-Reply-To: <20260627142740.3995235-1-ssbssa.ref@yahoo.de>
The CONTEXT_DEBUG_REGISTERS also includes the arch-specific bit
(CONTEXT_i386 or CONTEXT_AMD64) which is included in all CONTEXT_*
defines.
So this basically just checks if any CONTEXT_* define is set:
if ((context->ContextFlags & CONTEXT_DEBUG_REGISTERS) != 0)
And similarily, unsetting CONTEXT_DEBUG_REGISTERS removes the
arch-specific bit as well.
So this creates a CONTEXT_DEBUG_REG_FLAG define with just the
debug-registers bit, and uses it in these problematic locations.
---
gdb/x86-windows-nat.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/gdb/x86-windows-nat.c b/gdb/x86-windows-nat.c
index 27adeb1f154..3368814ed96 100644
--- a/gdb/x86-windows-nat.c
+++ b/gdb/x86-windows-nat.c
@@ -42,6 +42,10 @@ enum
#define DR6_CLEAR_VALUE 0xffff0ff0
+/* The CONTEXT_DEBUG_REGISTERS define without the arch-specific bit
+ (CONTEXT_i386 or CONTEXT_AMD64). */
+#define CONTEXT_DEBUG_REG_FLAG 0x10
+
struct x86_windows_per_inferior : public windows_per_inferior
{
/* The function to use in order to determine whether a register is
@@ -142,7 +146,7 @@ x86_windows_nat_target::thread_context_continue (windows_thread_info *th,
{
windows_process->fill_thread_context (th);
- gdb_assert ((context->ContextFlags & CONTEXT_DEBUG_REGISTERS) != 0);
+ gdb_assert ((context->ContextFlags & CONTEXT_DEBUG_REG_FLAG) != 0);
/* Check whether the thread has Dr6 set indicating a
watchpoint hit, and we haven't seen the watchpoint event
@@ -173,13 +177,13 @@ x86_windows_nat_target::thread_context_continue (windows_thread_info *th,
update the debug registers later when the thread
is re-resumed by the core after the watchpoint
event. */
- context->ContextFlags &= ~CONTEXT_DEBUG_REGISTERS;
+ context->ContextFlags &= ~CONTEXT_DEBUG_REG_FLAG;
}
}
else
DEBUG_EVENTS ("0x%x has no dr6 set", th->tid);
- if ((context->ContextFlags & CONTEXT_DEBUG_REGISTERS) != 0)
+ if ((context->ContextFlags & CONTEXT_DEBUG_REG_FLAG) != 0)
{
DEBUG_EVENTS ("0x%x changing dregs", th->tid);
context->Dr0 = state->dr_mirror[0];
--
2.54.0
next parent reply other threads:[~2026-06-27 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260627142740.3995235-1-ssbssa.ref@yahoo.de>
2026-06-27 14:27 ` Hannes Domani [this message]
2026-07-01 19:03 ` Pedro Alves
[not found] <96f2bcf2-96e5-46ea-9931-c9203415a9df () palves ! net>
2026-07-06 15:01 ` Hannes Domani
2026-07-21 15:02 ` Hannes Domani
2026-07-21 16:51 ` Tom Tromey
2026-07-22 12:24 ` Pedro Alves
2026-07-22 13:40 ` Tom Tromey
[not found] <590795675.1923429.1784732125709.ref@mail.yahoo.com>
2026-07-22 14:55 ` Hannes Domani
2026-07-22 15:55 ` Pedro Alves
[not found] <1310341683.1974283.1784737131422.ref@mail.yahoo.com>
2026-07-22 16:18 ` Hannes Domani
2026-07-23 19:04 ` Pedro Alves
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=20260627142740.3995235-1-ssbssa@yahoo.de \
--to=ssbssa@yahoo.de \
--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