* remote protocol: ambiguity of 'E*' response packets
@ 2009-07-07 3:49 Frank Ch. Eigler
2009-07-07 10:05 ` Pedro Alves
0 siblings, 1 reply; 2+ messages in thread
From: Frank Ch. Eigler @ 2009-07-07 3:49 UTC (permalink / raw)
To: gdb
Hi -
For the 'g' and 'm' query packets, it seems like a response packet
starting with "$E..." is entirely valid, if the register contents or
memory region starts with a 0xE0-0xEF byte. But remote.c:remote_send()
seems to interpret $E... anything as an error, and send_g_packet() uses
this one.
Am I misreading the code or the specs?
- FChE
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: remote protocol: ambiguity of 'E*' response packets
2009-07-07 3:49 remote protocol: ambiguity of 'E*' response packets Frank Ch. Eigler
@ 2009-07-07 10:05 ` Pedro Alves
0 siblings, 0 replies; 2+ messages in thread
From: Pedro Alves @ 2009-07-07 10:05 UTC (permalink / raw)
To: gdb; +Cc: Frank Ch. Eigler
On Tuesday 07 July 2009 04:49:46, Frank Ch. Eigler wrote:
> Hi -
>
> For the 'g' and 'm' query packets, it seems like a response packet
> starting with "$E..." is entirely valid, if the register contents or
> memory region starts with a 0xE0-0xEF byte. But remote.c:remote_send()
> seems to interpret $E... anything as an error, and send_g_packet() uses
> this one.
>
> Am I misreading the code or the specs?
Have the stub return lowercase hex digits [0-9a-z], like 0xe0-0xef
to work around it.
This is http://sourceware.org/bugzilla/show_bug.cgi?id=9665
--
Pedro Alves
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-07-07 10:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-07-07 3:49 remote protocol: ambiguity of 'E*' response packets Frank Ch. Eigler
2009-07-07 10:05 ` Pedro Alves
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox