You think in OpenOCD we could:
* discriminate between GDB "quit"/"detach" (reception of "$D#44") and GDB
"disconnect"/crash (TCP link lost):
* trigger two independent event handler "gdb-detach" and "gdb-disconnect"
(today the two cases falls in the same "gdb-detach")
* as in http://openocd.zylin.
This is an automated email from Gerrit.
Antonio Borneo (borneo.anto...@gmail.com) just uploaded a new patch set to
Gerrit, which you can find at http://openocd.zylin.com/6443
-- gerrit
commit a6f31f0f53cd0ec649958cce07b1f2345a5c3690
Author: Antonio Borneo
Date: Thu Aug 19 16:07:21 2021 +0200
Isn't that what Wren requests? If we do nothing to the target when the GDB
connection is dropped (killed GDB or lost connection) and resume the target
on the low level packet "$D#44" (detach).
However, it's not strictly specified that the target *should* resume when
GDB detaches. "Detaching from t
I have made some quick test on what GDB sends with the commands "quit",
"detach" and "disconnect". Either by using "-d" flag on OpenOCD side and with
command "set debug remote 1" at GDB side.
* "quit": GDB send the low-level packet "$D#44", then it exit
* "detach": GDB send the low-level packet "
