This is an automated email from Gerrit. Antonio Borneo ([email protected]) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/5600
-- gerrit commit ed44c987402db4089fa2c23b856e587e848326db Author: Antonio Borneo <[email protected]> Date: Fri Apr 24 15:11:29 2020 +0200 gdb: resume the target by default when gdb disconnects To quit from gdb or disconnect it from the remote, user has first to take control of the gdb console; this cause the remote target to be halted. Once quit or disconnects, the remote target is left halted, a condition that is not really useful. The documentation for the gdb command "detach" reports: When you have finished debugging the remote program, you can use the detach command to release it from GDB control. Detaching from the target normally resumes its execution, but the results will depend on your particular remote stub. The behaviour of gdbserver attached to a running process is to resume the process at gdb detach. Provide a default gdb-detach event that resumes the target. Change-Id: Ic8a38f154ca55f396b15002de8cf407161afc3d8 Signed-off-by: Antonio Borneo <[email protected]> diff --git a/src/target/startup.tcl b/src/target/startup.tcl index 976cd2a..a13b960 100644 --- a/src/target/startup.tcl +++ b/src/target/startup.tcl @@ -206,6 +206,7 @@ proc init_target_events {} { set_default_target_event $t gdb-flash-erase-start "reset init" set_default_target_event $t gdb-flash-write-end "reset halt" set_default_target_event $t gdb-attach "halt" + set_default_target_event $t gdb-detach "resume" } } -- _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
