Difference: UsingValgrind (1 vs. 2)

• Run valgrind [program], where [program] is what you would normally type to run your program, including all flags and arguments. This will give you a summary of memory leaks and basic memory errors.
• If you get memory leaks, try running valgrind --leak-check=full [program] to see exactly where leaks are happening. I believe this will make your program run a lot slower, so you may have to sit around and wait for a while. If it's too slow, try compiling with a higher optimization level.

Callgrind usage

• Compile code with -g flag.
• Run valgrind --tool=callgrind [program], where [program] is what you would normally type to run your program, including all flags and arguments.
• A file should be generated in your current working directory called callgrind.out.[pid], where [pid] is the pid of the process you just profiled.
• If you have kCacheGrind installed, you should be able to run the file just by double-clicking it, or type in the console: kcachegrind callgrind.out.[pid].
• If everything worked, you should now get a nice GUI view of your program's profile.
  • "Incl." is the time the function/method takes to run + the time all the functions it calls takes to run.
  • "Self" is the time the function/method takes to run excluding all functions it calls.
  • "Called" is the number of times the function was called.

Valgrind

Installation

• sudo apt-get install valgrind and it should do the rest.

KCacheGrind

here

• sudo apt-get install kcachegrind.

Memcheck usage

• Compile your code with -g -O0 flags. -g enables debugging mode and allows memcheck to display line numbers. -O0 compiles with no optimizations; higher levels can be used, but you might get false positives. Memcheck recommends using less than level O2.
  • Note: compiling with these flags can be done by setting the CMAKE_CXX_FLAGS and CMAKE_C_FLAGS variables in the main CMakeLists.txt file. Better yet, set a CMAKE_CXX_FLAGS_DEBUG and CMAKE_C_FLAGS_DEBUG and configure using ccmake to use compile a Debug version.
• Run valgrind , where is what you would normally type to run your program, including all flags and arguments. This will give you a summary of memory leaks and basic memory errors.
• If you get memory leaks, try running valgrind --leak-check=full to see exactly where leaks are happening. I believe this will make your program run a lot slower, so you may have to sit around and wait for a while. If it's too slow, try compiling with a higher optimization level.

Here's a nice overview of memcheck in general. Section 4.2 will give you a basic description of all the error messages, while section 4.3 will give you more command line options.