https://cs.indstate.edu/web/index.php?action=history&feed=atom&title=ValgrindValgrind - Revision history2026-04-14T21:49:37ZRevision history for this page on the wikiMediaWiki 1.44.0https://cs.indstate.edu/web/index.php?title=Valgrind&diff=429&oldid=prevJkinne: 1 revision imported2025-08-17T13:22:23Z<p>1 revision imported</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 13:22, 17 August 2025</td>
</tr><tr><td colspan="4" class="diff-notice" lang="en"><div class="mw-diff-empty">(No difference)</div>
</td></tr>
<!-- diff cache key wiki2:diff:1.41:old-428:rev-429 -->
</table>Jkinnehttps://cs.indstate.edu/web/index.php?title=Valgrind&diff=428&oldid=prevwiki_previous>Jkinne at 13:14, 15 November 20222022-11-15T13:14:02Z<p></p>
<p><b>New page</b></p><div>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>).<br />
<br />
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:<br />
<pre><br />
valgrind program_file.o<br />
</pre><br />
To see more detailed information about potential memory leaks, you can use the <code>--leak-check=full</code> option:<br />
<pre><br />
valgrind --leak-check=full program_file.o<br />
</pre><br />
<br />
More information about valgrind: https://valgrind.org/docs/manual/quick-start.html</div>wiki_previous>Jkinne