This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gdb-stub question (m packets)


>>>>> Andrew Cagney writes:

>> On Tue, Jul 23, 2002 at 01:05:36AM -0700, Alexei Minayev wrote:
>> 
>>> Dear gdb oracles,
>>> 
>>> I'm still fighting with my gdb-h8-stub, and getting funny yet evil errors.
>>> The gdb happens to attempt reading a memory location. The content of the
>>> memory location is something that starts with 0xE, say 0xE500.
>>> The conversation looks kinda like this:
>>> 
>>> m200042,2...Ack
>>> Packet received: E500
>>> Unable to access memory location 200042.
>>> 
>>> The gdb understands the numeric hex value of 0xE500 as an error response.
>>> So my question would be simple... am I supposed to prefix all my numeric
>>> packets with "0x"? Please help, this is confusing...
>> 
>> 
>> GDBserver uses lowercase hex numbers.  That seems to work fine.

> Hmm, can someone file a bug report for this: 
> http://sources.redhat.com/gdb/bugs/

> The error check should be for ``Enn'' (note the three digits - valid 
> responses would contain two or 4 digits).

Still, you have to use lower case. Otherwise a 1 byte read might be
mistaken for an error.

--Mark




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]