Hi Joel,
Gdb has command timeout.
By default, it is too short for a slow target like Pi.
Gdb hits the timeout and breaks.
You need to set the timeout to something large:
(gdb) set remotetimeout 1000
(gdb) target extended-remote 127.0.0.1:2000
Regards,
Eugene
From: tcf-dev-bounces@xxxxxxxxxxx <tcf-dev-bounces@xxxxxxxxxxx>
On Behalf Of Joel Sherrill
Sent: Sunday, November 29, 2020 12:48 PM
To: TCF Development <tcf-dev@xxxxxxxxxxx>
Subject: [tcf-dev] gdb remote protocol mismatch
CAUTION: This message has originated from an External Source. Please use proper judgment and caution
when opening attachments, clicking links, or responding to this email.
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?