From 224acfb0aad60018a273fa16c0125b695fe99f46 Mon Sep 17 00:00:00 2001 From: hjk Date: Fri, 19 Jun 2015 12:06:55 +0200 Subject: [PATCH] Valgrind: Remove one use of AnalyzerStartParameters::useStartupProject That information is now passed directly to the RunControl after its construction (and is still wrongly used afterwards to distinguish local from remote runs) Change-Id: Ifa21eea9f33b2602912cd3b1b2e884da4f53c0d9 Reviewed-by: Ulf Hermann --- src/plugins/valgrind/valgrindruncontrolfactory.cpp | 1 - 1 file changed, 1 deletion(-) diff --git a/src/plugins/valgrind/valgrindruncontrolfactory.cpp b/src/plugins/valgrind/valgrindruncontrolfactory.cpp index ac0e7d602e5..23b393d2bb8 100644 --- a/src/plugins/valgrind/valgrindruncontrolfactory.cpp +++ b/src/plugins/valgrind/valgrindruncontrolfactory.cpp @@ -97,7 +97,6 @@ RunControl *ValgrindRunControlFactory::create(RunConfiguration *runConfiguration sp.localRunMode = static_cast(rc1->runMode()); } else if (RemoteLinux::AbstractRemoteLinuxRunConfiguration *rc2 = qobject_cast(runConfiguration)) { - sp.useStartupProject = false; // FIXME: This is wrong. sp.debuggee = rc2->remoteExecutableFilePath(); sp.connParams = DeviceKitInformation::device(rc2->target()->kit())->sshParameters(); sp.debuggeeArgs = rc2->arguments().join(QLatin1Char(' '));