From f68588a58581a3169375b998ec6cf57509388986 Mon Sep 17 00:00:00 2001
From: Christian Stenger <christian.stenger@qt.io>
Date: Mon, 21 Oct 2019 09:24:51 +0200
Subject: [PATCH] RemoteLinux: Correct clean shutdown when debugging

If the inferior stops by itself and the debugger
tries to shutdown it had ended up waiting forever for
the additional workers (e.g. ports gatherer, channel
provider,...) to stop.
The debugger appeared as finished but the runworker was
still in a running state until the user would hit the stop
button of the application output pane.
Make the gdbserver essential to initiate a clean finish.

Change-Id: I16b2ebe5feadc88bb76ce34b49ac5d3456d0867c
Reviewed-by: hjk <hjk@qt.io>
---
 src/plugins/remotelinux/remotelinuxdebugsupport.cpp | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/plugins/remotelinux/remotelinuxdebugsupport.cpp b/src/plugins/remotelinux/remotelinuxdebugsupport.cpp
index 5143efe7d95..a9a3eca3a1e 100644
--- a/src/plugins/remotelinux/remotelinuxdebugsupport.cpp
+++ b/src/plugins/remotelinux/remotelinuxdebugsupport.cpp
@@ -42,6 +42,7 @@ LinuxDeviceDebugSupport::LinuxDeviceDebugSupport(RunControl *runControl)
     addQmlServerInferiorCommandLineArgumentIfNeeded();
 
     auto gdbServer = new GdbServerRunner(runControl, portsGatherer());
+    gdbServer->setEssential(true);
 
     addStartDependency(gdbServer);