From: Andrew Cagney <ac131313@redhat.com>
To: Jan Hoogerbrugge <hoogerbrugge@hotmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Endianness and remote debugging
Date: Tue, 22 Apr 2003 17:06:00 -0000 [thread overview]
Message-ID: <3EA576A2.9060106@redhat.com> (raw)
In-Reply-To: <Law9-F103M9Y17VVZxM0000a316@hotmail.com>
> The problem has been solved after that I discovered that register values are sent in target order while other values are sent in big endian order.
>
> BWT, I was refering to the 'qPmodethreadid' query of section D.4.
Ah, yes, that ID is in network byte order.
Andrew
next prev parent reply other threads:[~2003-04-22 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 10:51 Jan Hoogerbrugge
2003-04-22 17:06 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-17 14:42 Jan Hoogerbrugge
2003-04-21 14:05 ` Andrew Cagney
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=3EA576A2.9060106@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=hoogerbrugge@hotmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).