feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Debugger: Don't wait for responses for flushing dummy commands

Browse Source 
As this is also used after -exec-continue we won't see a result
before the next stop and consequently run into the watchdog
timeout regularly.

Change-Id: Ibb7e42ae1810d4d9f536cf755219fba6d8aa0f96
Reviewed-by: Orgad Shaneh <orgads@gmail.com>
This commit is contained in:
hjk
2021-09-08 09:49:30 +02:00
parent 939cc5af21
commit 7cc4e27184
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
src/plugins/debugger/gdb/gdbengine.cpp
View File

@@ -784,8 +784,11 @@ void GdbEngine::runCommand(const DebuggerCommand &command)
QMetaObject::invokeMethod(this, [this, buffer] { handleResponse(buffer); });
} else {
m_gdbProc.write(cmd.function.toUtf8() + "\r\n");
if (command.flags & NeedsFlush)
runCommand({"p 0"});
if (command.flags & NeedsFlush) {
// We don't need the response or result here, just want to flush
// anything that's still on the gdb side.
m_gdbProc.write({"p 0\n"});
}
// Start Watchdog.
if (m_commandTimer.interval() <= 20000)
@@ -857,7 +860,7 @@ void GdbEngine::handleResultRecord(DebuggerResponse *response)
//qDebug() << "\nRESULT" << response->token << response->toString();
int token = response->token;
if (token == -1)
if (token <= 0)
return;
if (!m_commandForToken.contains(token)) {