gdb-stub question (m packets)

gdb-stub question (m packets)

[Alexei Minayev]

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

Thanks
Regards -- Alexei

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com

Re: gdb-stub question (m packets)

[Daniel Jacobowitz]

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.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

Re: gdb-stub question (m packets)

[Quality Quorum]

On Tue, 23 Jul 2002, 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...

You have to use lower case for number strings.


>
> Thanks
> Regards -- Alexei
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Health - Feel better, live better
> http://health.yahoo.com
>

Thanks,

Aleksey

Re: gdb-stub question (m packets)

[Andrew Cagney]

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

Andrew

Re: gdb-stub question (m packets)

[Mark Salter]

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

Re: gdb-stub question (m packets)

[Mark Salter]

>>>>> Mark Salter writes:

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

Nevermind. I obviously can't count.

--Mark

Re: gdb-stub question (m packets)

[Alexei Minayev]

Thanks for helping out, everyone.

Regards -- Alexei

--- Daniel Jacobowitz <drow@mvista.com> wrote:
> GDBserver uses lowercase hex numbers.  That seems to work fine.
> 
> -- 
> Daniel Jacobowitz                           Carnegie Mellon University
> MontaVista Software                         Debian GNU/Linux Developer


__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com