Commit e37b1bdf authored by hjk's avatar hjk
Browse files

Debugger: Work around lazy GDB communication



-exec-finish in 'main' results (correctly) in something like
 40^error,msg="\"finish\" not meaningful in the outermost frame."
However, this message does not seem to get flushed before
anything else happens - i.e. "never". So force some extra output
that's known to trigger a flush.

Change-Id: I3f5ef6f7cc57dd085976b239f18d6ec7bd108972
Reviewed-by: default avatarNiels Weber <niels.weber@theqtcompany.com>
parent b6037215
......@@ -2093,6 +2093,11 @@ void GdbEngine::executeStepOut()
notifyInferiorRunRequested();
showStatusMessage(tr("Finish function requested..."), 5000);
postCommand("-exec-finish", RunRequest, CB(handleExecuteContinue));
// -exec-finish in 'main' results (correctly) in
// 40^error,msg="\"finish\" not meaningful in the outermost frame."
// However, this message does not seem to get flushed before
// anything else happen - i.e. "never". Force some extra output.
postCommand("print 32");
}
void GdbEngine::executeNext()
......
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