This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Endianness and remote debugging
- From: "Jan Hoogerbrugge" <hoogerbrugge at hotmail dot com>
- To: ac131313 at redhat dot com
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 22 Apr 2003 12:51:52 +0200
- Subject: Re: Endianness and remote debugging
- Bcc:
My target runs in little endian and my host in big endian. On the line
between the stub and gdb I see that data is communicated in little endian.
That seems to work fine. However, queries dealing with thread stuff seem
to assume big endian. For example, I see the mode field of the P query in
big endian. Is this a bug or am I missing something?
You mean the P (write register) packet? According to the documentation
(http://sources.redhat.com/gdb/, follow documentation), the register value
is in target byte order.
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.
Thanks,
Jan
_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8.
http://join.msn.com/?page=features/junkmail