From: Daniel Jacobowitz <drow@false.org>
To: Guillaume MENANT <guillaume.menant@geensys.com>
Cc: gdb@sourceware.org
Subject: Re: Data order in GDB commands
Date: Wed, 23 Jan 2008 14:11:00 -0000 [thread overview]
Message-ID: <20080123141123.GA4216@caradoc.them.org> (raw)
In-Reply-To: <15042357.post@talk.nabble.com>
On Wed, Jan 23, 2008 at 06:04:45AM -0800, Guillaume MENANT wrote:
>
> I'm wondering what is the order of the data in the GDB commands like (G, g,
> m, M...)
>
> If i receive G0022f600...
>
> What should I write in my register ? 0x0022F600 or 0x00F62200 or something
> else ?
You should be able to figure this out by experimentation, very
easily. Set a register to a value and see what packet GDB sends.
It's target byte order.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-01-23 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 14:05 Guillaume MENANT
2008-01-23 14:11 ` 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=20080123141123.GA4216@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=guillaume.menant@geensys.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