From: Gary Benson <gbenson@redhat.com>
To: Walfred Tedeschi <walfred.tedeschi@intel.com>
Cc: palves@redhat.com, eliz@gnu.org, brobecker@adacore.com,
gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] amd64: add fs_base and gs_base
Date: Wed, 30 Nov 2016 14:20:00 -0000 [thread overview]
Message-ID: <20161130142016.GA12916@blade.nx> (raw)
In-Reply-To: <1478166445-21370-1-git-send-email-walfred.tedeschi@intel.com>
Hi Walfred,
Walfred Tedeschi wrote:
> The next two patches add Linux system registers fs_base and gs_base
> in GDB and gdbserver.
>
> First commit align the gdbserver with GDB code in terms of
> HAVE_STRUCT_USER_REGS_STRUCT_(GS|FS)_BASE.
>
> Second patch introduces the registers into GDB and gdbserver.
I tried this with the Infinity stuff I'm doing today and it's working
great. The only change I had to make was to add the new registers to
amd64_dwarf_regmap with the patch below.
Thanks,
Gary
--
diff --git a/gdb/amd64-tdep.c b/gdb/amd64-tdep.c
index a3a1fde..d0450cc 100644
--- a/gdb/amd64-tdep.c
+++ b/gdb/amd64-tdep.c
@@ -223,8 +223,8 @@ static int amd64_dwarf_regmap[] =
-1,
/* Segment Base Address Registers. */
- -1,
- -1,
+ AMD64_FSBASE_REGNUM,
+ AMD64_GSBASE_REGNUM,
-1,
-1,
prev parent reply other threads:[~2016-11-30 14:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 9:47 Walfred Tedeschi
2016-11-03 9:47 ` [PATCH 2/2] amd64-linux: expose system register FS_BASE and GS_BASE for Linux Walfred Tedeschi
2016-11-05 14:55 ` John Baldwin
2016-11-07 14:40 ` Tedeschi, Walfred
2016-11-10 12:36 ` Gary Benson
2016-11-30 13:31 ` Tedeschi, Walfred
2016-11-23 12:02 ` Pedro Alves
2016-11-30 10:29 ` Tedeschi, Walfred
2016-12-07 16:37 ` Pedro Alves
[not found] ` <1478166445-21370-2-git-send-email-walfred.tedeschi@intel.com>
2016-11-10 12:37 ` [PATCH 1/2] gdbserver-amd64: add HAVE_STRUCT_USER_REGS_STRUCT_(GS|FS)_BASE for gdbserver Gary Benson
2016-11-23 12:02 ` Pedro Alves
2016-11-30 14:20 ` Gary Benson [this message]
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=20161130142016.GA12916@blade.nx \
--to=gbenson@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=walfred.tedeschi@intel.com \
/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