From: Mark Salter <msalter@redhat.com>
To: ac131313@ges.redhat.com
Cc: drow@mvista.com, aminayev@yahoo.com, gdb@sources.redhat.com
Subject: Re: gdb-stub question (m packets)
Date: Tue, 23 Jul 2002 07:58:00 -0000 [thread overview]
Message-ID: <200207231455.g6NEteK28861@deneb.localdomain> (raw)
In-Reply-To: <3D3D6CF2.1020708@ges.redhat.com> (message from Andrew Cagney on Tue, 23 Jul 2002 10:49:22 -0400)
>>>>> 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
next prev parent reply other threads:[~2002-07-23 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 1:05 Alexei Minayev
2002-07-23 5:29 ` Daniel Jacobowitz
2002-07-23 7:49 ` Andrew Cagney
2002-07-23 7:58 ` Mark Salter [this message]
2002-07-23 8:01 ` Mark Salter
2002-07-24 10:28 ` Alexei Minayev
2002-07-23 5:30 ` Quality Quorum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200207231455.g6NEteK28861@deneb.localdomain \
--to=msalter@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=aminayev@yahoo.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox