Difference between revisions of "Valgrind"
(Created page with "First, you should make sure to compile your program with debugging information enabled. See GNU Debugger. You can run the <code>valgrind</code> memory checker by running...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | Note that <code>valgrind</code> is installed on cs.indstate.edu but not on all of the lab desktops, so make sure you are logged into cs in the terminal (e.g., <code>ssh username@cs.indstate.edu</code>). | ||
| + | |||
First, you should make sure to compile your program with debugging information enabled. See [[GNU Debugger]]. You can run the <code>valgrind</code> memory checker by running: | First, you should make sure to compile your program with debugging information enabled. See [[GNU Debugger]]. You can run the <code>valgrind</code> memory checker by running: | ||
<pre> | <pre> | ||
valgrind program_file.o | valgrind program_file.o | ||
</pre> | </pre> | ||
| + | To see more detailed information about potential memory leaks, you can use the <code>--leak-check=full</code> option: | ||
| + | <pre> | ||
| + | valgrind --leak-check=full program_file.o | ||
| + | </pre> | ||
| + | |||
| + | More information about valgrind: https://valgrind.org/docs/manual/quick-start.html | ||
Latest revision as of 13:14, 15 November 2022
Note that valgrind is installed on cs.indstate.edu but not on all of the lab desktops, so make sure you are logged into cs in the terminal (e.g., ssh username@cs.indstate.edu).
First, you should make sure to compile your program with debugging information enabled. See GNU Debugger. You can run the valgrind memory checker by running:
valgrind program_file.o
To see more detailed information about potential memory leaks, you can use the --leak-check=full option:
valgrind --leak-check=full program_file.o
More information about valgrind: https://valgrind.org/docs/manual/quick-start.html
