[cdt-debug-dev] Terminate debug session for embedded development

[Øyvind Harboe <oyvind.harboe@xxxxxxxxx>]

> Agreed, for this it should be handle in the backend of the debugger.
> debugSession.terminate() means ... finish/kaput/dead/over/flatline and we go through
> the drill i.e. Process.destroy() ... but on some system "gdb a` la peau dure"
> i.e. the thing is hard to kill. 

So let me try to translate this:

If GDB does not die within a second or two, then CDT is to terminate it.

If the session does not terminate after a couple of seconds and CDT
seems stuck, then the bug is almost certainly in the Eclipse process
termination code.

Fixing the bug in the process termination code can turn out to be a
nasty bug to fix.


This is a bit strange, because I have not yet encountered a stuck GDB
where the Windows Task Manager or "kill -9" under Linux has had any
problems.

-- 
Øyvind Harboe
http://www.zylin.com