From f2a5932674749b248b42b04b166fa2f621fcbfec Mon Sep 17 00:00:00 2001 From: hjk Date: Wed, 16 May 2018 14:46:53 +0200 Subject: [PATCH] Debugger: Remove a too strict error handling There's seems to be the possibility to actually trigger the assert this patch removes with MinGW and mixed debugging. While the reason for that is not clear yet, there's no need to force the debugger to abort. The observer wrong state was InferiorRunOk, so just continuing on the selected path will do the right thing (i.e. attempt to interrupt the debugged process) Change-Id: I534cedd71522e73d5f1097ddd472efbeb3b4d97f Reviewed-by: Eike Ziller Reviewed-by: Christian Stenger --- src/plugins/debugger/gdb/gdbengine.cpp | 1 - 1 file changed, 1 deletion(-) diff --git a/src/plugins/debugger/gdb/gdbengine.cpp b/src/plugins/debugger/gdb/gdbengine.cpp index 410c30944ce..a635bed613f 100644 --- a/src/plugins/debugger/gdb/gdbengine.cpp +++ b/src/plugins/debugger/gdb/gdbengine.cpp @@ -696,7 +696,6 @@ void GdbEngine::interruptInferior() showStatusMessage(tr("Stop requested..."), 5000); showMessage("TRYING TO INTERRUPT INFERIOR"); if (HostOsInfo::isWindowsHost() && !m_isQnxGdb) { - QTC_ASSERT(state() == InferiorStopRequested, qDebug() << state(); notifyInferiorStopFailed()); IDevice::ConstPtr device = runTool()->device(); if (!device) device = runParameters().inferior.device;