From: Pedro Alves <palves@redhat.com>
To: Richard Henderson <rth@redhat.com>,
Gary Benson <gbenson@redhat.com>,
"H.J. Lu" <hjl.tools@gmail.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: Changes required for x86 address spaces
Date: Wed, 21 Oct 2015 18:36:00 -0000 [thread overview]
Message-ID: <5627DB32.2040208@redhat.com> (raw)
In-Reply-To: <5627CFB6.1050809@redhat.com>
On 10/21/2015 06:47 PM, Richard Henderson wrote:
> I was thinking the same thing. Presumably all one needs to do is define new
> architecture registers and fill in the blanks. But I've lost track of how to
> do that these days; it seems to be scattered across 19 different files...
Yeah, on x86-64, fs_base and fs_base are available in user_regs_struct
nowadays, thus accessible with PTRACE_PEEKUSER and PTRACE_GETREGSET.
Basically you need to:
- add new gdb register numbers to amd64-tdep.h
- add the ptrace/gdb register mapping to amd64-linux-tdep.c:amd64_linux_gregset_reg_offset
- add new xml files to gdb/features/i386/
- make gdb/x86-linux-nat.c:x86_linux_read_description return the new description.
Thanks,
Pedro Alves
prev parent reply other threads:[~2015-10-21 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 22:25 Richard Henderson
2015-10-21 2:38 ` H.J. Lu
2015-10-21 8:16 ` Gary Benson
2015-10-21 17:47 ` Richard Henderson
2015-10-21 18:36 ` Pedro Alves [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=5627DB32.2040208@redhat.com \
--to=palves@redhat.com \
--cc=gbenson@redhat.com \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=rth@redhat.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