From: Guillaume MENANT <guillaume.menant@geensys.com>
To: gdb@sourceware.org
Subject: Data order in GDB commands
Date: Wed, 23 Jan 2008 14:05:00 -0000 [thread overview]
Message-ID: <15042357.post@talk.nabble.com> (raw)
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 ?
Thanks a lot for your answers :)
--
View this message in context: http://www.nabble.com/Data-order-in-GDB-commands-tp15042357p15042357.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.
next reply other threads:[~2008-01-23 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 14:05 Guillaume MENANT [this message]
2008-01-23 14:11 ` Daniel Jacobowitz
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=15042357.post@talk.nabble.com \
--to=guillaume.menant@geensys.com \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).