How to interpret (encoded?) gdb response

[Daniel Jacobowitz]

On Thu, Aug 14, 2008 at 11:13:08AM +0200, Andr? P?nitz wrote:
> 
> Hi all.
> 
> I do the foillowing:
> 
>   - run an inferior containing a tight endless loop
>   - attach to it with gdb -pid=<id>
>   - run  'kill <pid>' in shell
>   - do  -exec-continue
> 
> then I get:
> 
>   67^running
>   (gdb) 
>   &"Cannot access memory at address 0x7fff6ca72a4c\n"
>   &"\240\240\354\003\n"
>   67^error,msg="\240\240\354\003"
> 
> Does that msg have any meaning, i.e. how would I "decode" it?
> The message appears also in a non-MI environment, but is even
> less legible there...

No, it's some sort of bug or bad pointer.  Does this happen in HEAD?

-- 
Daniel Jacobowitz
CodeSourcery