Endianness and remote debugging

Endianness and remote debugging

[Jan Hoogerbrugge]

Hi,

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?

(I am using gdb 5.3)

Thanks,
Jan





_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail

Re: Endianness and remote debugging

[Andrew Cagney]

> Hi,
> 
> 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.

Andrew

Re: Endianness and remote debugging

[Andrew Cagney]

> 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

Re: Endianness and remote debugging

[Jan Hoogerbrugge]

>>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