From: John Baldwin <jhb@freebsd.org>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Support fs_base and gs_base for native FreeBSD/amd64
Date: Tue, 11 Jul 2017 16:26:00 -0000 [thread overview]
Message-ID: <1760319.A5fLcXoheI@ralph.baldwin.cx> (raw)
In-Reply-To: <86wp7fqur3.fsf@gmail.com>
On Tuesday, July 11, 2017 08:48:32 AM Yao Qi wrote:
> John Baldwin <jhb@FreeBSD.org> writes:
>
> > On the other hand, I wonder if we shouldn't just add fs_base and gs_base
> > to the "core" descriptions alongside "fs" and "gs" rather than using a
> > separate feature if they are always going to be present.
>
> The feature org.gnu.gdb.i386.core and org.gnu.gdb.i386.segments are
> already explicitly documented
> https://sourceware.org/gdb/current/onlinedocs/gdb/i386-Features.html
> I don't think we can modify org.gnu.gdb.i386.core.
Ok.
--
John Baldwin
prev parent reply other threads:[~2017-07-11 16:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 22:50 John Baldwin
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
[not found] ` <CAH=s-PPM7u=f=_4k+=wLvv4z822VJRqbkxrsSv9C0eKqX-tMCA@mail.gmail.com>
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-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
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 [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=1760319.A5fLcXoheI@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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