Development/Tools/Valgrind - Revision history

Mpyne: Add --track-origins flag for valgrind

2009-07-16T02:44:57Z

Add --track-origins flag for valgrind

Pino: {{file}} -> {{path}}

2007-05-28T23:53:46Z

{{file}} -> {{path}}

Pino: use {{file}}

2007-03-07T14:11:22Z

use {{file}}

Pino: add some basic instructions about using valgrind for memleak checking

2007-03-05T21:00:38Z

add some basic instructions about using valgrind for memleak checking

CuCullin: Fixed a link

2007-01-08T21:43:17Z

Fixed a link

Cullmann: Valgrind moved to Development/Tools/Valgrind

2006-09-28T14:53:11Z

Valgrind moved to Development/Tools/Valgrind

Dhaumann: Tool -> tool

2006-09-24T12:35:49Z

Tool -> tool

Tstaerk at 15:30, 23 September 2006

2006-09-23T15:30:16Z

New page

Valgrind is a [[Tool]] to analyze a program regarding memory leaks
* [http://www.valgrind.org/ The Valgrind Homepage]
* [http://www.tldp.org/HOWTO/Valgrind-HOWTO/ Excellent tutorial at TLDP]

@@ Line 15: / Line 15: @@
 * executing valgrind with <tt>--leak-check=full</tt> instead of <tt>--leak-check=yes</tt> can give a more detailed output, especially about the found leaks
 == References ==
 * [http://www.valgrind.org/ The Valgrind Homepage]
 * [http://www.tldp.org/HOWTO/Valgrind-HOWTO/ Excellent tutorial at TLDP]

@@ Line 10: / Line 10: @@
 As valgrind can produce a lot of output (and thus scroll out of your terminal), you can call valgrind redirecting its output to a file, so nothing gets lost.
   > valgrind --tool=memcheck --leak-check=yes -v ''appname'' 2>&1 | tee valgrind.log
-This will call valgrind as seen above, and will redirect all the output coming from both our application and valgrind to a file in the current directory called {{file|valgrind.log}} (of course it is possible to use any file name of the log).
+This will call valgrind as seen above, and will redirect all the output coming from both our application and valgrind to a file in the current directory called {{path|valgrind.log}} (of course it is possible to use any file name of the log).
 === Minor tweaks ===

@@ Line 9: / Line 9: @@
 As valgrind can produce a lot of output (and thus scroll out of your terminal), you can call valgrind redirecting its output to a file, so nothing gets lost.
-  > valgrind --tool=memcheck --leak-check=yes -v ''appname'' 2>&1 | tee ''valgrind.log''
+  > valgrind --tool=memcheck --leak-check=yes -v ''appname'' 2>&1 | tee valgrind.log
-This will call valgrind as seen above, and will redirect all the output coming from both our application and valgrind to a file in the current directory falled ''valgrind.log'' (of course it is possible to use any file name of the log).
+This will call valgrind as seen above, and will redirect all the output coming from both our application and valgrind to a file in the current directory called {{file|valgrind.log}} (of course it is possible to use any file name of the log).
 === Minor tweaks ===

@@ Line 1: / Line 1: @@
-Valgrind is a [[Tools|tool]] to analyze a program regarding memory leaks
+Valgrind is a [[Development/Tools|tool]] to analyze a program regarding memory leaks.
 * [http://www.valgrind.org/ The Valgrind Homepage]
 * [http://www.tldp.org/HOWTO/Valgrind-HOWTO/ Excellent tutorial at TLDP]