[avr-gcc-list] another bug with gdb 5.3 :-(

[Klaus Rudolph]

Hi all,


I have another reproduceable error in gdb 5.3.

Everytime the simulavr raise an irq and jumps to the vector
while gdb is looking for the next instruction with a "$s#xx"
there come a lot of T.... , thats fine, but then
the next T... comes with the irqvector in the PC. (4000000 -> Vector
Address 0x40
Also OK. But now gdb tries to read memory
m00,27 means read memory from flash 0x00 with 0x27 bytes long
next is
m27,19 means from 0x27 flash address with 0x19 bytes size.
after receiving that data the gdb allways crashes.

Have you any idea how to debug gdb with gdb?
I tried it, but sending a singint to the subprocess 
is received by the debugging debugger itself :-(

If I attach from the outside world with gdb --pid xxxx to
the avr-gdb I got sometimes the same problem, sometimes
I got a communication protocol error between the 
avr-gdb and simulavr :-(

The avr-gdb 5.3 is absolutly unusable :-(

Any tips & tricks here.

Thanks
        Klaus