You can profile remote projects just as local ones. This can be useful when developing an application for a different architecture.
+
To run Valgrind remotely, right-click a remote c/c++ project and navigate to "Profile As", then "Profile Configurations". In the new window, double-click the Profile with Valgrind (remote) profile configuration.
+
In the main tab, click "Browse" under "C/C++ executable" to choose the binary that will be executed. The same tool configurations for local projects apply to remote ones.
+
+
+
+
After configuring the profile, click the Profile button to launch the profile. Results will be displayed in the same Valgrind view previously described.
+
+
\ No newline at end of file
diff --git a/valgrind/org.eclipse.linuxtools.valgrind.doc/Linux_Tools_Project/Valgrind/User_Guide/Special-Cases.html b/valgrind/org.eclipse.linuxtools.valgrind.doc/Linux_Tools_Project/Valgrind/User_Guide/Special-Cases.html
index c12ec0cca2..3e4cea4db4 100644
--- a/valgrind/org.eclipse.linuxtools.valgrind.doc/Linux_Tools_Project/Valgrind/User_Guide/Special-Cases.html
+++ b/valgrind/org.eclipse.linuxtools.valgrind.doc/Linux_Tools_Project/Valgrind/User_Guide/Special-Cases.html
@@ -12,7 +12,7 @@
All the synchronization errors found by Helgrind are displayed in the Valgrind view, which appears automatically after a profile run. Each displayed error can be expanded in the Valgrind view to display its stack trace.
-
+
In some cases, Helgrind can determine which section of the source code causes a reported error. Whenever this is the case, double-clicking on the stack trace of the reported error will open the related source file and place the cursor on the line responsible for the error. This stack trace view is similar to the view that the Memcheck plug-in provides.
+
+ 
+
+ 
+ 
+
+ 
+ 