[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] Terminate debug session for embedded development
|
>
> > 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 d=
> ure"
> > i.e. the thing is hard to kill.=20
>
> So let me try to translate this:
>
> If GDB does not die within a second or two, then CDT is to terminate it.
>
Yes there is a termination timeout before coecirve force is taken.
> 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.
>
Not sure you can blame Eclipse for this, the code is doing what is
available:
java.lang.Process.destroy()
> Fixing the bug in the process termination code can turn out to be a
> nasty bug to fix.
>
The question is why this does not work :
- is it a bug in our termination sequence ?
- some sort of race condition ?
- why it seem to happen in your environment.
- is your gdb version flaky ?
- .. etc ...
>
> 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.
>
Kill -9 is not available in Java ... and we are not sure taking out the
nuclear arsenal is the good approach to deal with this issue.
