This mode is useless, has not sense, and complicates a code
handling. A more useful equivalent for this mode is
"Debug->Start Debugging->Attach to Running Debug Server".
Change-Id: I863dbc5c41ca82db52792a3ff2a1eae16f8e7afd
Reviewed-by: hjk <hjk@qt.io>
We don't need in this class, because the remote GDB servers are
launches by the RunWorker.
Besides, the BareMetalDevice::canCreateProcess() and the
BareMetalDevice::createProcess() are not even gets called at all.
Tested with the STM32 Nucleo-F767ZI board using the ST-Util GDB provider.
Change-Id: I8d3770ec59738c63aa44dd39d371a1b443a81f9a
Reviewed-by: hjk <hjk@qt.io>
The BareMetalDevice and the BareMetalDebugSupport classes should
not know anything about the specific implementation of the providers.
For this purpose, we just extend a providers by a new virtual methods
which are should be overridden for a concrete provider.
Change-Id: Ic5fef49f6b79e0ee7e8c4c386b4ed36cb5346dc1
Reviewed-by: hjk <hjk@qt.io>
