Changes between Version 2 and Version 3 of EclipseAndMoleCuilder

Timestamp:

Feb 26, 2010, 12:21:27 PM (15 years ago)

Author:

FrederikHeber

Comment:

Linuxtools respectively valgrind added

EclipseAndMoleCuilder

@@ -5 +5 @@
    * ECUT >1.0M3
    * Eclipse Git >0.5.0
+   * Linuxtools >0.4.1
+
+Note that some general advice on using eclipse can be found [here http://wissrech.ins.uni-bonn.de/inside/wikka/Eclipse].
 
 == Configuring CDT ==
@@ -43 +46 @@
 Finally, we configure a run configuration for this new executable. Select '''Run''' from the menu and '''Run Configurations'''. Select ''!CppUnit'' in the list on the left. Click on the '''new launch configuration''' in the icon list above. Give the test a decent name, select your project, use the build configuration you created above (!CppUnitTest) and finally '''Search Project''' for the new executable. Click '''Apply''' and '''Run'''. 
 
+Note that from now no you can easily access the created Profile by its name in the '''Run''' menu under '''Run as'''.
+
 A new tab should appear called !CppUnit with an icon featuring a green letter C and a red letter U. Therein, the errors of the tests are listed. A green bar indicates whether everything ran fine. The green start button re-runs the test executable. 
 
@@ -53 +58 @@
 Eclipse should now display the current branch in square brackets next to the project name in the project explorer. Furthermore, in the context menu, in the '''team''' subitem you find items such as '''Commit''', '''Branch''', '''!ResetTo''', ... resembling some of commands of git for easy use inside eclipse.
 
+== Linuxtools ==
+
+The Linuxtools package contain the support for autotools that we have configured above already, but also support for profilers and code checkers such as [valgrind http://www.valgrind.org/]. Some general remarks on [debugging http://wissrech.ins.uni-bonn.de/inside/wikka/Debuggen] and [profiling http://wissrech.ins.uni-bonn.de/inside/wikka/Profilieren] can be found in the Inside wiki in german.
+
+Running valgrind within eclipse has the advantage that memory errors can be directly associated with the respective responsible code lines. Proceed as follows:
+In the '''Run''' menu, select '''Profile configurations''' to create a configuration of the command you wish to run under valgrind's authority. Select '''Profile with Valgrind''' from the left-hand menu. Click on the '''new launch configuration''' in the icon list above. Give the test a decent name, e.g. ''Valgrinding !TestRunner'', select your project, use the build configuration you created above (!CppUnitTest) and finally '''Search Project''' for the new executable, here ''!TestRunner''. If you need to run more complex commands, arguments and can be given in the '''Arguments''' tab. In the '''Valgrind options''' command line options of valgrind can be specified. You might want to change the '''Leak resolution''' there to ''full'' and check the '''Show reachable blocks''' for full report on memory leaks and reachable adresses. Also make sure to have your Project listed in the '''Source''' tab, if not '''Add''' it. Click '''Apply''' and '''Profile'''. 
+
+Note that now you can easily access the created Profile by its name in the '''Run''' menu under '''Profile as'''.