Valgrind is a tool that can be used to detect memory management and threading bugs.
- Download the latest Valgrind source code from http://valgrind.org/downloads/. For example, this downloads version 3.12.0:
Shell1~$ wget http://valgrind.org/downloads/valgrind-3.12.0.tar.bz2
- Unpack the tarball with
C1~$ tar -jxvf valgrind-3.12.0.tar.bz2
cd into the root directory of the unpacked source code.
Shell1~$ cd valgrind-3.12.0
- Install valgrind onto your system with:
Shell1~/valgrind-3.12.0$ sudo make install
- Done! You should now be able to run valgrind by typing:
from any directory in your shell.
Profiling With Valgrind
The most simple way to run a program with valgrind is to call valgrind and pass in the executable at the only parameter:
~$ valgrind ./profiling_test
This will run Memcheck, a memory error detector. Expect your program to run 4-10x slower!
To run callgrind, use the following command:
~$ valgrind --tool=callgrind ./profiling_test
NOTE: The order of the optional parameters to valgrind is important! Make sure –tool=callgrind comes BEFORE the path to your executable.
WARNING: Again, callgrind will make your program run 4-10x slower than usual. If this slow down is unacceptable for whatever reason, but you still want to profile your application, you may want to check out GCC’s gprof which in my experience, causes much less of a performance drop.
This will generate a profile data file called callgrind.out.<pid> in the same folder as the exectuable. To display the results of the profiling:
~$ callgrind_annotate callgrind.out.<pid>
–dump-instr=yes allows you to get profile information at the instruction level.
However, this text can be hard to analyze! Thankfully, there is a visual tool called kcachegrind which can create visual graphs from the callgrind output (yes, kCACHEgrind can display the results of CALLgrind). kcachegrind can be installed on Ubuntu with:
$ sudo apt install kcachegrind
Be warned, kcachegrind could require around 350MB of space! I recommend you install kcachegrind on your development machine rather than embedded Linux.
kcachegrind can then be started by calling kcachegrind in the same directory as the cachegrind output data file:
You should then be presented with wonderful profiling data as shown below!
Posted: June 13th, 2017 at 5:53 am
Last Updated on: November 18th, 2017 at 7:30 am