Community
Participate
Working Groups
1- Set the preference to not kill GDB when the last inferior exits 2- use a post-mortem session 3- Press terminate on the process or thread or stack frame 574,950 [MI] 34-interpreter-exec console kill 574,953 [MI] ~"Kill the program being debugged? (y or n) [answered Y; input not from terminal]\n" 574,954 [MI] &"You can't do that without a process to debug.\n" 574,954 [MI] 34^error,msg="You can't do that without a process to debug." We should check for the type of debug session before choose how we terminate
Created attachment 192432 [details] Fix This patch checks if we are dealing with a post-mortem session, and if so, a terminate request will always terminate GDB, instead of trying 'kill' on the inferior. Committed to HEAD.
Fixed. John, can you review? (3 lines)
*** cdt cvs genie on behalf of mkhouzam *** Bug 339591: Cannot use 'kill' in a post-mortem session [*] GDBProcesses.java 1.24 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBProcesses.java?root=Tools_Project&r1=1.23&r2=1.24 [*] GDBProcesses_7_0.java 1.47 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/gdb/service/GDBProcesses_7_0.java?root=Tools_Project&r1=1.46&r2=1.47
Looks good to me
