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

debugger: fix problem where a manual 'continue' was needed after start up.

Browse Source 
The problem was that the 'emptyness' of m_cookieForToken was used as an
indication that there was no response packet still in the air. However,
this hash was not reset after a debugging session was aborted using S-F5,
so it could contain items from a previous run, effectively preventing
automatic triggering of the necessary 'continue'.
This commit is contained in:
hjk
2009-06-29 13:28:01 +02:00
parent cc3a57a93a
commit ae3ac786e0
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -198,6 +198,7 @@ void GdbEngine::initializeVariables()
m_autoContinue = false; m_autoContinue = false;
m_waitingForFirstBreakpointToBeHit = false; m_waitingForFirstBreakpointToBeHit = false;
m_commandsToRunOnTemporaryBreak.clear(); m_commandsToRunOnTemporaryBreak.clear();
m_cookieForToken.clear();
} }
void GdbEngine::gdbProcError(QProcess::ProcessError error) void GdbEngine::gdbProcError(QProcess::ProcessError error)
@@ -1361,6 +1362,10 @@ int GdbEngine::currentFrame() const
bool GdbEngine::startDebugger(const QSharedPointer<DebuggerStartParameters> &sp) bool GdbEngine::startDebugger(const QSharedPointer<DebuggerStartParameters> &sp)
{ {
// This should be set by the constructor or in exitDebugger().
QTC_ASSERT(m_debuggingHelperState == DebuggingHelperUninitialized,
initializeVariables());
debugMessage(DebuggerSettings::instance()->dump()); debugMessage(DebuggerSettings::instance()->dump());
QStringList gdbArgs; QStringList gdbArgs;