forked from qt-creator/qt-creator
Fix non-stop mode in gdb when you click continue
When you hit a brekpoint in gdb non-stop mode, if you click continue in the
UI the debugger was killed if the current thread is not the one being
stopped. This is anoying as gdb does not change current thread
automatically. The fix shows the error but does not kill the inferior.
Fixed style issues again.
Reviewed-by: hjk <qthjk@ovi.com>
(cherry picked from commit 47def926c7)
Change-Id: I18e8b77b615cfceec402b140337709074ad96dc5
Reviewed-by: hjk <qthjk@ovi.com>
This commit is contained in:
@@ -1801,6 +1801,9 @@ void GdbEngine::handleExecuteContinue(const GdbResponse &response)
|
||||
// FIXME: Fix translation in master.
|
||||
showStatusMessage(QString::fromLocal8Bit(msg), 5000);
|
||||
gotoLocation(stackHandler()->currentFrame());
|
||||
} else if (msg.startsWith("Cannot execute this command while the selected thread is running.")) {
|
||||
showExecutionError(QString::fromLocal8Bit(msg));
|
||||
notifyInferiorRunFailed() ;
|
||||
} else {
|
||||
showExecutionError(QString::fromLocal8Bit(msg));
|
||||
notifyInferiorIll();
|
||||
|
||||
Reference in New Issue
Block a user