< Guidelines and HOWTOs‎ | Debugging
Revision as of 12:34, 11 March 2016 by Ochurlaud (talk | contribs) (Ochurlaud moved page Guidelines and HOWTOs/Valgrind to Guidelines and HOWTOs/Debugging/Valgrind)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Guidelines and HOWTOs/Debugging/Valgrind

Valgrind is a tool to analyze a program regarding memory leaks.

Leak Detection

One of the valgrind tools is the memcheck, that can be used to detect memory leaks during the execution of an application.

To do that, valgrind can be started as:

> valgrind --tool=memcheck --leak-check=yes -v appname

where appname is the application you want to run, including its parameters, if it have to be called with any.

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 valgrind.log (of course it is possible to use any file name of the log).

Minor tweaks

  • executing valgrind with --leak-check=full instead of --leak-check=yes can give a more detailed output, especially about the found leaks
  • Using the --track-origins=yes flag is even slower than normal Valgrind but gives you the location where the memory used incorrectly was allocated in many situations.


This page was last edited on 11 March 2016, at 12:34. Content is available under Creative Commons License SA 4.0 unless otherwise noted.