From 30c21397a6edb808a29ab1fc770f616ea8690d36 Mon Sep 17 00:00:00 2001 From: Kai Koehne <kai.koehne@nokia.com> Date: Tue, 6 Mar 2012 09:21:27 +0100 Subject: [PATCH] QmlDebugger: Close connection already in shutdownInferior Doing it in shutdownEngine was too late for the mixed debugger case: The client has already exited in this case, leading to error messages on the (system) console. Change-Id: Id31214cb7a1bc9530c1da78b872531bc79894f3b Reviewed-by: Aurindam Jana <aurindam.jana@nokia.com> --- src/plugins/debugger/qml/qmlengine.cpp | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/plugins/debugger/qml/qmlengine.cpp b/src/plugins/debugger/qml/qmlengine.cpp index 5df56a20e25..c84ea15d855 100644 --- a/src/plugins/debugger/qml/qmlengine.cpp +++ b/src/plugins/debugger/qml/qmlengine.cpp @@ -628,14 +628,13 @@ void QmlEngine::shutdownInferior() resetLocation(); } stopApplicationLauncher(); + closeConnection(); notifyInferiorShutdownOk(); } void QmlEngine::shutdownEngine() { - closeConnection(); - // double check (ill engine?): stopApplicationLauncher(); -- GitLab