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

Analyzer: no need to pass a start mode when it's implicit in the name.

Browse Source 
startRemoteTool and startLocalTool are implcicitely working remotely and localy, they don't need a mode.

Change-Id: I433ca421f68a1026979489c7f9d86b12251ec830
Reviewed-by: hjk <qthjk@ovi.com>
This commit is contained in:
Nicolas Arnaud-Cormos
2011-12-27 17:28:24 +01:00
committed by hjk
parent 29eff52529
commit 1571b7f977
3 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/plugins/valgrind/valgrindplugin.cpp
View File

@@ -165,7 +165,7 @@ RunConfigWidget *ValgrindRunControlFactory::createConfigurationWidget(RunConfigu
//
/////////////////////////////////////////////////////////////////////////////////
static void startRemoteTool(IAnalyzerTool *tool, StartMode mode)
static void startRemoteTool(IAnalyzerTool *tool)
{
Q_UNUSED(tool);
StartRemoteDialog dlg;
@@ -174,7 +174,7 @@ static void startRemoteTool(IAnalyzerTool *tool, StartMode mode)
AnalyzerStartParameters sp;
sp.toolId = tool->id();
sp.startMode = mode;
sp.startMode = StartRemote;
sp.connParams = dlg.sshParams();
sp.debuggee = dlg.executable();
sp.debuggeeArgs = dlg.arguments();
@@ -191,9 +191,9 @@ static void startRemoteTool(IAnalyzerTool *tool, StartMode mode)
void ValgrindPlugin::startValgrindTool(IAnalyzerTool *tool, StartMode mode)
{
if (mode == StartLocal)
AnalyzerManager::startLocalTool(tool, mode);
AnalyzerManager::startLocalTool(tool);
if (mode == StartRemote)
startRemoteTool(tool, mode);
startRemoteTool(tool);
}
static AbstractAnalyzerSubConfig *globalValgrindFactory()