Debugger: Remove the InferiorExited state

There are now several possible orders of events between sending a 'kill'
and receiving something that indicated a properly shut down inferior.
Coordinating the InferiorExited state during engine ramp down is not
worthwhile as that state had only a forced transition to InferiorShutdownOk
anyway. For the user (and user code), only the fact that ramp down is
finished is interesting.

Change-Id: Ic22131d5a1066dc62bd069f532c28b773f231088
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>

1 files changed, 0 insertions, 6 deletions

diff --git a/src/plugins/debugger/qml/qmlcppengine.cpp b/src/plugins/debugger/qml/qmlcppengine.cpp
index baef8df87c..69d905acf4 100644
--- a/src/plugins/debugger/qml/qmlcppengine.cpp
+++ b/src/plugins/debugger/qml/qmlcppengine.cpp
@@ -649,12 +649,6 @@ void QmlCppEngine::slaveEngineStateChanged
             notifyInferiorStopFailed();
             break;
         }
-        case InferiorExitOk: {
-            // InferiorExitOk will be called through notifyInferiorExited
-            // when InferiorShutDownOk is reached
-            qmlEngine()->quitDebugger();
-            break;
-        }
         case InferiorShutdownRequested: {
             if (state() == InferiorStopOk) {
                 setState(InferiorShutdownRequested);