From: Yao Qi <qiyaoltc@gmail.com>
To: John Baldwin <jhb@FreeBSD.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Support the fs_base and gs_base registers on FreeBSD/amd64 native processes.
Date: Tue, 11 Jul 2017 08:09:00 -0000 [thread overview]
Message-ID: <86o9srqtxw.fsf@gmail.com> (raw)
In-Reply-To: <20170627224948.99138-3-jhb@FreeBSD.org> (John Baldwin's message of "Tue, 27 Jun 2017 15:49:48 -0700")
John Baldwin <jhb@FreeBSD.org> writes:
> Use ptrace operations to fetch and store the fs_base and gs_base registers
> for FreeBSD/amd64 processes. Note that FreeBSD does not currently store the
> value of these registers in core dumps, so these registers are only
> available when inspecting a running process.
>
> gdb/ChangeLog:
>
> * amd64-bsd-nat.c (amd64bsd_fetch_inferior_registers): Use
> PT_GETFSBASE and PT_GETGSBASE.
> (amd64bsd_store_inferior_registers): Use PT_SETFSBASE and
> PT_SETGSBASE.
The patch is good to me.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-07-11 8:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 22:50 [PATCH 0/2] Support fs_base and gs_base for native FreeBSD/amd64 John Baldwin
2017-06-27 22:51 ` [PATCH 2/2] Support the fs_base and gs_base registers on FreeBSD/amd64 native processes John Baldwin
2017-07-11 8:09 ` Yao Qi [this message]
2017-06-27 22:51 ` [PATCH 1/2] Include the fs_base and gs_base registers in amd64 target descriptions John Baldwin
2017-07-11 8:03 ` Yao Qi
2017-07-11 16:26 ` John Baldwin
2017-07-12 12:16 ` Phil Muldoon
2017-07-12 13:02 ` Yao Qi
2017-07-12 13:51 ` Simon Marchi
2017-07-12 20:03 ` John Baldwin
2017-07-13 16:55 ` Yao Qi
2017-07-13 17:04 ` John Baldwin
2017-07-13 18:40 ` Pedro Alves
2017-07-13 19:59 ` Pedro Alves
2017-07-12 16:23 ` Keith Seitz
2017-07-11 7:49 ` [PATCH 0/2] Support fs_base and gs_base for native FreeBSD/amd64 Yao Qi
2017-07-11 16:26 ` 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=86o9srqtxw.fsf@gmail.com \
--to=qiyaoltc@gmail.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).