From: Daniel Jacobowitz <drow@false.org>
To: Ananth Sowda <asowda@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: remote protocol target byte ordering question
Date: Tue, 01 Jul 2008 02:14:00 -0000 [thread overview]
Message-ID: <20080701021431.GA15520@caradoc.them.org> (raw)
In-Reply-To: <c92b40c80806301842l3671c69iaa7fbc0163a5266d@mail.gmail.com>
On Mon, Jun 30, 2008 at 06:42:09PM -0700, Ananth Sowda wrote:
> I know that GDB remote protocol uses target byte ordering for
> multi-bytes values as in register set content, memory address or
> values to be written to the target memory. I don't see where in the
> GDB code this swapping from host to target byte order is done. Can
> someone point to the right segment of the code? Thanks for any
> pointers.
Everywhere. The gdb convention is that all buffers are in target byte
order. For instance, follow extract_unsigned_integer.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-07-01 2:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 1:42 Ananth Sowda
2008-07-01 2:14 ` Daniel Jacobowitz [this message]
2008-07-01 19:12 ` Michael Snyder
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=20080701021431.GA15520@caradoc.them.org \
--to=drow@false.org \
--cc=asowda@gmail.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