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.com/#/c/5600/ use a default "gdb-detach" that runs "resume" * keep empty the default "gdb-disconnect", or with a silly "echo disconnected" ?
--- ** [tickets:#314] quit doesn't properly detach** **Status:** new **Milestone:** 0.11.0 **Created:** Thu Aug 19, 2021 05:02 AM UTC by Wren Turkal **Last Updated:** Thu Aug 19, 2021 09:04 AM UTC **Owner:** nobody The quit command is supposed to detach (and thus continue) the inferior before exiting. If one wants to disconnect without continuing the inferior, there is also a disconnect command. I noticed this change: http://openocd.zylin.com/#/c/5600/1 Here's the gdb docs on attach/detach: https://ftp.gnu.org/old-gnu/Manuals/gdb/html_node/gdb_22.html Here's the gdb docs on detach/disconnect: https://sourceware.org/gdb/current/onlinedocs/gdb/Connecting.html#Connecting It would be lovely to have the right semantics so that quiting continues while disconnect does not change the execution state to match these semantics. --- Sent from sourceforge.net because openocd-devel@lists.sourceforge.net is subscribed to https://sourceforge.net/p/openocd/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
