From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <dan@codesourcery.com>,
mark.kettenis@xs4all.nl, teawater@gmail.com,
msnyder@vmware.com, gdb-patches@sourceware.org,
hjl.tools@gmail.com
Subject: Re: [RFA 3/5] Prec: x86 segment register support: target
Date: Mon, 22 Mar 2010 18:14:00 -0000 [thread overview]
Message-ID: <e394668d1003221114m7787468ekdd0a6bdc4004e070@mail.gmail.com> (raw)
In-Reply-To: <83sk7sgrm3.fsf@gnu.org>
On Mon, Mar 22, 2010 at 11:04 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Mon, 22 Mar 2010 10:53:35 -0400
>> From: Daniel Jacobowitz <dan@codesourcery.com>
>> Cc: teawater@gmail.com, msnyder@vmware.com, gdb-patches@sourceware.org, hjl.tools@gmail.com
>>
>> On Mon, Mar 22, 2010 at 03:33:55PM +0100, Mark Kettenis wrote:
>> > Sorry, but I don't think adding these xx_base registers is a good
>> > idea. They are not acrhitected registers so they don't beling in the
>> > list of registers.
>>
>> What do you suggest instead?
>
> Would a separate command fit the bill? (The DJGPP build already has
> something similar, see "info dos ldt" and its description in the
> manual with an example of how to use it to display the DS segment base
> address and limit.)
I'd have the regs in a separate info command (out of "info regs"),
there's more than just base, there's the limit and flags regs too, and
having them would really reduce the S/N ratio of "info reg", but
having $gs_base, et.al. usable in expressions is really useful (and
long overdue). Either that or make "gs:<offset>" as an address work -
you'd still want to be able to fold it to a "flat" address though.
next prev parent reply other threads:[~2010-03-22 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 16:53 Hui Zhu
2010-03-16 18:12 ` Michael Snyder
2010-03-16 20:04 ` Daniel Jacobowitz
2010-03-22 14:03 ` Hui Zhu
2010-03-22 14:35 ` H.J. Lu
2010-03-22 14:44 ` Hui Zhu
2010-03-22 15:05 ` Mark Kettenis
2010-03-22 14:35 ` Mark Kettenis
2010-03-22 14:45 ` Hui Zhu
2010-03-22 14:53 ` Daniel Jacobowitz
2010-03-22 18:04 ` Eli Zaretskii
2010-03-22 18:14 ` Doug Evans [this message]
2010-03-22 16:03 ` Doug Evans
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=e394668d1003221114m7787468ekdd0a6bdc4004e070@mail.gmail.com \
--to=dje@google.com \
--cc=dan@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=mark.kettenis@xs4all.nl \
--cc=msnyder@vmware.com \
--cc=teawater@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