Skip to content

profiling.md

Latest commit

 

History

History
22 lines (17 loc) · 642 Bytes

profiling.md

File metadata and controls

22 lines (17 loc) · 642 Bytes

Profiling the C++ testing engine

We use valgrind for profiling the engine on Linux and WSL.

To install valgrind run:

sudo apt-get install -y valgrind

To profile an executable that is using the C++ testing engine run:

valgrind --tool=callgrind <PATH_TO_EXECUTABLE>

This will dump a file named callgrind.out.<PID> (where <PID> was the process id of the executable that just run).

To see the stacks, run:

callgrind_annotate  callgrind.out.<PID>

To see counts for each statement (rather than just at a function level) add the --auto=yes option. To see inclusive results add the --inclusive=yes option.