[tcf-dev] gdb remote protocol mismatch

[Joel Sherrill <joel@xxxxxxxxx>]

Hi

I hope someone recognizes this. As a behavioral reference, we have been using the tcf-agent on a Pi4 and either Eclipse on a CentOS VM or the gdb native to the Pi. It works without apparent issue with Eclipse but attaching the Pi gdb (8.2.1) directly gives this:

(gdb) target extended-remote 192.168.1.12:2000
Remote debugging using 192.168.1.12:2000
Remote replied unexpectedly to 'vMustReplyEmpty': PacketSize=4000;QStartNoAckMode+;qXfer:features:read+;qXfer:exec-file:read+;multiprocess+;swbreak+;hwbreak+

Same thing happens with the regular remote target protocol.

If there some obvious reason the gdb server in tcf-agent would have an issue talking to gdb like this? 

Thanks.

--joel sherrill

RTEMS