Clear old analyzer issues on tool start.

Change-Id: I54f7791c15e05ca5c85c8b4059f80b050de57282
Reviewed-by: hjk <hjk@theqtcompany.com>

src/plugins/analyzerbase/analyzermanager.cpp

@@ -52,6 +52,7 @@
 #include <projectexplorer/buildconfiguration.h>
 #include <projectexplorer/session.h>
 #include <projectexplorer/target.h>
+#include <projectexplorer/taskhub.h>
 
 #include <utils/algorithm.h>
 #include <utils/fancymainwindow.h>
@@ -420,6 +421,7 @@ bool AnalyzerManagerPrivate::showPromptDialog(const QString &title, const QStrin
 void AnalyzerManagerPrivate::startTool()
 {
     QTC_ASSERT(m_currentAction, return);
+    TaskHub::clearTasks(Constants::ANALYZERTASK_ID);
     m_currentAction->toolStarter()();
 }
 

src/plugins/valgrind/memcheckengine.cpp

@@ -44,7 +44,6 @@
 #include <projectexplorer/project.h>
 #include <projectexplorer/projectexplorer.h>
 #include <projectexplorer/target.h>
-#include <projectexplorer/taskhub.h>
 #include <projectexplorer/toolchain.h>
 
 #include <utils/qtcassert.h>
@@ -82,9 +81,6 @@ bool MemcheckRunControl::startEngine()
 {
     m_runner.setParser(&m_parser);
 
-    // Clear about-to-be-outdated tasks.
-    TaskHub::clearTasks(Analyzer::Constants::ANALYZERTASK_ID);
-
     appendMessage(tr("Analyzing memory of %1").arg(executable()) + QLatin1Char('\n'),
                         Utils::NormalMessageFormat);
     return ValgrindRunControl::startEngine();