Commit 4e992d8d authored by cnavarro's avatar cnavarro Committed by hjk

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: default avatarhjk <qthjk@ovi.com>
(cherry picked from commit 47def926)

Change-Id: I18e8b77b615cfceec402b140337709074ad96dc5
Reviewed-by: default avatarhjk <qthjk@ovi.com>
parent e5ebe089
......@@ -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();
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment