* gdb-stub question (m packets)
@ 2002-07-23 1:05 Alexei Minayev
2002-07-23 5:29 ` Daniel Jacobowitz
2002-07-23 5:30 ` Quality Quorum
0 siblings, 2 replies; 7+ messages in thread
From: Alexei Minayev @ 2002-07-23 1:05 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: gdb-stub question (m packets)
2002-07-23 1:05 gdb-stub question (m packets) Alexei Minayev
@ 2002-07-23 5:29 ` Daniel Jacobowitz
2002-07-23 7:49 ` Andrew Cagney
2002-07-24 10:28 ` Alexei Minayev
2002-07-23 5:30 ` Quality Quorum
1 sibling, 2 replies; 7+ messages in thread
From: Daniel Jacobowitz @ 2002-07-23 5:29 UTC (permalink / raw)
To: Alexei Minayev; +Cc: gdb
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: gdb-stub question (m packets)
2002-07-23 5:29 ` Daniel Jacobowitz
@ 2002-07-23 7:49 ` Andrew Cagney
2002-07-23 7:58 ` Mark Salter
2002-07-24 10:28 ` Alexei Minayev
1 sibling, 1 reply; 7+ messages in thread
From: Andrew Cagney @ 2002-07-23 7:49 UTC (permalink / raw)
To: Daniel Jacobowitz, Alexei Minayev; +Cc: gdb
> 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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: gdb-stub question (m packets)
2002-07-23 7:49 ` Andrew Cagney
@ 2002-07-23 7:58 ` Mark Salter
2002-07-23 8:01 ` Mark Salter
0 siblings, 1 reply; 7+ messages in thread
From: Mark Salter @ 2002-07-23 7:58 UTC (permalink / raw)
To: ac131313; +Cc: drow, aminayev, gdb
>>>>> 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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: gdb-stub question (m packets)
2002-07-23 5:29 ` Daniel Jacobowitz
2002-07-23 7:49 ` Andrew Cagney
@ 2002-07-24 10:28 ` Alexei Minayev
1 sibling, 0 replies; 7+ messages in thread
From: Alexei Minayev @ 2002-07-24 10:28 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: gdb-stub question (m packets)
2002-07-23 1:05 gdb-stub question (m packets) Alexei Minayev
2002-07-23 5:29 ` Daniel Jacobowitz
@ 2002-07-23 5:30 ` Quality Quorum
1 sibling, 0 replies; 7+ messages in thread
From: Quality Quorum @ 2002-07-23 5:30 UTC (permalink / raw)
To: Alexei Minayev; +Cc: gdb
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
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2002-07-24 17:28 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-07-23 1:05 gdb-stub question (m packets) Alexei Minayev
2002-07-23 5:29 ` Daniel Jacobowitz
2002-07-23 7:49 ` Andrew Cagney
2002-07-23 7:58 ` Mark Salter
2002-07-23 8:01 ` Mark Salter
2002-07-24 10:28 ` Alexei Minayev
2002-07-23 5:30 ` Quality Quorum
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox