[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] Re: [cdt-patch] MISession terminate patch
|
>
> Hi Alain,
>
> i've just tried this, but i can still get into a state where the suspend
> event is still running by the time the inferior has been destroyed. =20
>
> I've managed to isolate a reproducible case for this. In this case, the
> inferior terminates (kill sent out) while the EventManager is in the
> middle of the processSuspendedEvent function.=20
Yes I see where you're going.
The problem with the approach is that the GDB session becomes inaccessible.
No other commands will pass through except "show exit code". You may
want to access legitimate information from GDB.
For example, folks with big applications(~ 500Megs) loading the debug symbols can take
a __very__ long time. So they may want to contribute an action, "restart/rerun"
that will reissue another "run" in gdb after the kill.
It is something we are planning for the future.
Lets poke around a little more, before falling back to your proposed patch.
