Valgrind: Fix "alien binary" filtering for remote analyzing.

The current implementation thinks an executed binary does not belong to
the project if it is not located in the build directory. However, for
remote analyzing, that file is never started from the build directory,
but from the place it was deployed to.

Change-Id: Iaaf473aac1cf90aa2300ab7c36b92008e269690a
Reviewed-by: hjk <hjk121@nokiamail.com>

src/plugins/valgrind/memchecktool.cpp

@@ -48,6 +48,7 @@
 #include <extensionsystem/iplugin.h>
 #include <extensionsystem/pluginmanager.h>
 
+#include <projectexplorer/deploymentdata.h>
 #include <projectexplorer/projectexplorer.h>
 #include <projectexplorer/project.h>
 #include <projectexplorer/runconfiguration.h>
@@ -144,6 +145,11 @@ bool MemcheckErrorFilterProxyModel::filterAcceptsRow(int sourceRow, const QModel
         foreach (Project *project, SessionManager::projects()) {
             validFolders << project->projectDirectory();
             foreach (Target *target, project->targets()) {
+                foreach (const ProjectExplorer::DeployableFile &file,
+                         target->deploymentData().allFiles()) {
+                    if (file.isExecutable())
+                        validFolders << file.remoteDirectory();
+                }
                 foreach (BuildConfiguration *config, target->buildConfigurations())
                     validFolders << config->buildDirectory().toString();
             }