From: Eli Zaretskii <eliz@gnu.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: msnyder@vmware.com, gdb-patches@sourceware.org
Subject: Re: PATCH: Support x86 pseudo registers
Date: Wed, 03 Mar 2010 17:33:00 -0000 [thread overview]
Message-ID: <83sk8h2tum.fsf@gnu.org> (raw)
In-Reply-To: <6dc9ffc81003021407l27b513cbm288d1fd1e43d0c46@mail.gmail.com>
> Date: Tue, 2 Mar 2010 14:07:41 -0800
> From: "H.J. Lu" <hjl.tools@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
>
> >>> I presume it lets us say $ah or $ax in addition to $eax, and lets $eax
> >>> work on 64-bit systems where we really have $rax.
> >>
> >> Mmm hmm, and the context would be expressions or anywhere where a
> >> register name is appropriate (eg. info reg). Â Yes?
> >>
> >
> > Yes.
> >
> > (top-gdb) info reg $edi
> > edi       0x1    1
> > (top-gdb) info reg $rdi
> > rdi       0x1    1
> > (top-gdb) info reg $dl
> > dl       0xd8   -40
> > (top-gdb) info reg $dil
> > dil       0x1    1
> > (top-gdb)
> >
> >
>
> Basically, you can access any byte/word/dword registers, as shown
> in assembly code, the same way as word/dword registers.
Then how about this entry:
* X86 general purpose registers
GDB now supports reading/writing byte, word and double-word x86
general purpose registers directly. This means you can use, say,
$ah or $ax to refer, respectively, to the byte register AH and
16-bit word register AX that are actually portions of the 32-bit
register EAX or 64-bit register RAX.
next prev parent reply other threads:[~2010-03-03 17:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 17:02 H.J. Lu
2010-03-02 11:17 ` Mark Kettenis
2010-03-02 13:55 ` Daniel Jacobowitz
2010-03-02 14:08 ` H.J. Lu
2010-03-02 15:04 ` Daniel Jacobowitz
2010-03-02 15:37 ` H.J. Lu
2010-03-02 17:54 ` Eli Zaretskii
2010-03-02 19:01 ` H.J. Lu
2010-03-02 20:54 ` Eli Zaretskii
2010-03-02 21:06 ` H.J. Lu
2010-03-02 21:47 ` Eli Zaretskii
2010-03-02 21:52 ` Daniel Jacobowitz
2010-03-02 21:57 ` Michael Snyder
2010-03-02 22:00 ` H.J. Lu
2010-03-02 22:07 ` H.J. Lu
2010-03-03 17:33 ` Eli Zaretskii [this message]
2010-03-03 17:53 ` H.J. Lu
2010-03-03 18:09 ` Eli Zaretskii
2010-03-03 20:20 ` H.J. Lu
2010-03-12 4:23 ` Pedro Alves
2010-03-12 5:32 ` H.J. Lu
2010-03-12 6:07 ` H.J. Lu
2010-03-12 18:22 ` Michael Snyder
2010-03-12 8:30 ` Eli Zaretskii
2010-03-12 15:26 ` Pedro Alves
2010-03-12 16:04 ` Eli Zaretskii
2010-03-12 16:30 ` Daniel Jacobowitz
2010-03-12 18:14 ` Eli Zaretskii
2010-03-12 18:20 ` Pedro Alves
2010-03-12 18:55 ` Eli Zaretskii
2010-03-12 19:47 ` H.J. Lu
2010-03-12 16:31 ` Pedro Alves
2010-03-02 21:58 ` H.J. Lu
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=83sk8h2tum.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=msnyder@vmware.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