From: Tom Tromey <tromey@adacore.com>
To: John Baldwin <jhb@FreeBSD.org>
Cc: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Mask x86 segment registers in Windows gdbserver
Date: Thu, 21 Dec 2023 13:29:42 -0700 [thread overview]
Message-ID: <87wmt72tah.fsf@tromey.com> (raw)
In-Reply-To: <3c3d8d0c-8e61-46c0-88d5-fecce4112b59@FreeBSD.org> (John Baldwin's message of "Wed, 20 Dec 2023 14:03:12 -0800")
>> 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.
John> LGTM. Treating the x86 seg regs as 32-bits has required workarounds in
John> various places, but not easily fixable unfortunately.
Well, to my surprise, this patch caused regressions in our internal
tester.
It works again if I explicitly exclude the 'ss' register, like:
if (!windows_process.wow64_process)
return r >= AMD64_CS_REGNUM && r <= AMD64_GS_REGNUM && r != 19;
Now, this seems "ok" to do in some sense. However, I can't explain why
native gdb works fine, as it has the same logic in
amd64_windows_segment_register_p.
I'd welcome any thoughts you (or anybody) might have.
Tom
next prev parent reply other threads:[~2023-12-21 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 14:48 Tom Tromey
2023-12-20 22:03 ` John Baldwin
2023-12-21 20:29 ` Tom Tromey [this message]
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=87wmt72tah.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.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).