forked from qt-creator/qt-creator
Analyzer: Move tool startup code closer to the action setup
The code sharing in the base was along a somewhat unfortunate boundary. Moving it into the only user also removes some of the wrong local/remote separation. Change-Id: I0be9636ea448d123f9f5105a52d56f47ff7871c3 Reviewed-by: Ulf Hermann <ulf.hermann@theqtcompany.com>
This commit is contained in:
@@ -594,42 +594,12 @@ void MemcheckTool::setBusyCursor(bool busy)
|
||||
m_errorView->setCursor(cursor);
|
||||
}
|
||||
|
||||
void MemcheckTool::startLocalTool()
|
||||
{
|
||||
if (checkForLocalStart(DebugMode))
|
||||
ProjectExplorerPlugin::runStartupProject(MemcheckRunMode);
|
||||
}
|
||||
|
||||
void MemcheckTool::startRemoteTool()
|
||||
{
|
||||
AnalyzerStartParameters sp;
|
||||
if (checkForRemoteStart(&sp)) {
|
||||
AnalyzerRunControl *rc = createRunControl(sp, 0);
|
||||
ProjectExplorerPlugin::startRunControl(rc, MemcheckRunMode);
|
||||
}
|
||||
}
|
||||
|
||||
MemcheckWithGdbTool::MemcheckWithGdbTool(QObject *parent) :
|
||||
MemcheckTool(parent)
|
||||
{
|
||||
setObjectName(QLatin1String("MemcheckWithGdbTool"));
|
||||
}
|
||||
|
||||
void MemcheckWithGdbTool::startLocalTool()
|
||||
{
|
||||
if (checkForLocalStart(DebugMode))
|
||||
ProjectExplorerPlugin::runStartupProject(MemcheckWithGdbRunMode);
|
||||
}
|
||||
|
||||
void MemcheckWithGdbTool::startRemoteTool()
|
||||
{
|
||||
AnalyzerStartParameters sp;
|
||||
if (checkForRemoteStart(&sp)) {
|
||||
AnalyzerRunControl *rc = createRunControl(sp, 0);
|
||||
ProjectExplorerPlugin::startRunControl(rc, MemcheckWithGdbRunMode);
|
||||
}
|
||||
}
|
||||
|
||||
MemcheckRunControl *MemcheckWithGdbTool::createMemcheckRunControl(const AnalyzerStartParameters &sp,
|
||||
RunConfiguration *runConfiguration)
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user