forked from qt-creator/qt-creator
Debugger: Move some code around
Parts of the Debugger engine rampdown mechanisms are essentially one code path now, don't distribute that over four classes. Change-Id: I4c6edbc0db94d1f658b0c1d9c154552f286db876 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
This commit is contained in:
@@ -603,12 +603,6 @@ void DebuggerRunTool::start()
|
||||
m_engine->start();
|
||||
}
|
||||
|
||||
void DebuggerRunTool::startFailed()
|
||||
{
|
||||
appendMessage(tr("Debugging has failed"), NormalMessageFormat);
|
||||
m_engine->handleStartFailed();
|
||||
}
|
||||
|
||||
void DebuggerRunTool::stop()
|
||||
{
|
||||
m_isDying = true;
|
||||
@@ -616,13 +610,6 @@ void DebuggerRunTool::stop()
|
||||
m_engine->quitDebugger();
|
||||
}
|
||||
|
||||
void DebuggerRunTool::debuggingFinished()
|
||||
{
|
||||
appendMessage(tr("Debugging has finished"), NormalMessageFormat);
|
||||
Internal::runControlFinished(this);
|
||||
reportStopped();
|
||||
}
|
||||
|
||||
const DebuggerRunParameters &DebuggerRunTool::runParameters() const
|
||||
{
|
||||
return m_runParameters;
|
||||
|
Reference in New Issue
Block a user