From: Daniel Jacobowitz <drow@mvista.com>
To: Anthony Booker <tb@cray.com>
Cc: gdb@sources.redhat.com
Subject: Re: x86_64 register cache layout
Date: Fri, 12 Dec 2003 00:34:00 -0000 [thread overview]
Message-ID: <20031212003416.GA11046@nevyn.them.org> (raw)
In-Reply-To: <1071188179.30671.61.camel@boom.wc.cray.com>
On Thu, Dec 11, 2003 at 04:16:19PM -0800, Anthony Booker wrote:
> Hello gdb,
>
> I am trying to implement a simple remote protocol server for an AMD
> Opteron based system. I am happily getting exchanges back and forth,
> I'm ignoring a whole bunch of comands but eventually gdb settles down
> and says it's attached to the remote process. I can modify memory on
> the target and see the effects on the process.
>
> What I'd like to do is have the 'g' command actually provide register
> contents, preferably all the registers and preferably the real data. :)
>
> To do this I'll need to find the right packing order for the reply
> frame. From my reading so far I believe this is, with a couple of minor
> exceptions, the hex string representation of the register cache.
>
> So I follow the bouncing ball and get down to supply_register which
> calls register data which uses reg_defs to define the order and length
> of entries in the cache.
>
> Now reg_defs seems to be set set_register_cache but I can't find where
> that is called. I did attach to a gdbserver and found that the caller
> seems to give regs_x86_64 as the initialiser. But I can find neither
> hide nor hair of that variable in the gdb source I have and the
> gdbserver is sans symbols. So I'm stuffed.
>
> Can anyone help me join the final dot and locate the table?
Take a look at regformats/reg-x86-64.dat.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-12-12 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 0:16 Anthony Booker
2003-12-12 0:34 ` Daniel Jacobowitz [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=20031212003416.GA11046@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=tb@cray.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