[Simulavr-devel] Trying again to implement GDB "target remote | simulavr"

[Joel Lehtonen]

Hi!

I read your mailing list archives and found out you have had multiple
threads about implementing gdb's "target remote |" support, that is running
simulavr directly from gdb to avoid allocating TCP port which has some
security disadvantages.

I found a bit low-quality patch from
http://lists.nongnu.org/archive/html/simulavr-devel/2011-03/msg00000.html,
made by Petr Hluzín. I managed to get it compile current master with some
manual merging. Here's my patch:

https://github.com/zouppen/simulavr/compare/target_remote

However, when I started the patched simulavr from avr-gdb prompt, it never
returns:

(gdb) target remote | simulavr --gdb-stdin -d atmega328
Remote debugging using | simulavr --gdb-stdin -d atmega328
Using gdb client in stdin/stdout.
Ignoring packet error, continuing...
warning: unrecognised item "timeout" in "qSupported" response
Ignoring packet error, continuing...
^[Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
warning: Invalid remote reply: timeout
...

But anyway, if you would like to make it working, you may fix my patch and
put it upstream. I have so narrow knowledge of your code base so it would
take me days to fix it...

PS. If you're curious about what I'm working with: It's an LED cube driver
(running on ATmega328) and I'm trying to do some scripting with simulavr
and gdb to extract memory contents periodically from AVR and pass the
output to Blender. That would become much more straightforward if I would
be able to invoke simulavr inside a gdb script.

-- 
Joel