https://www.hardening-consulting.com/enTue, 18 Feb 2025 22:51:03 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://www.hardening-consulting.com/en/posts/20240618-valgrind-and-massif.htmlDavid FORT<div><p><img class="alignright" src="https://www.hardening-consulting.com/images/valgrind.png" width="100px"> A little tip that I discovered some time ago: the <code>massive</code> tool from <code>valgrind</code>. It can address cases where we have a program that eats up too much memory unnecessarily, but since it does cleanups correctly at the end, we don't see anything with standard leak tools like <code>valgrind</code> or <code>asan</code>.</p> <p><br style="clear: both;"></p> <h2>Massif</h2> <p>This is where the <code>massif</code> tool from <code>valgrind</code> comes in as well as the <code>massif-visualizer</code> visualization tool. This tool will allow you to regularly take snapshots of memory allocations, and to see the callstacks of location in our programs that make these allocations.</p> <p><a href="https://www.hardening-consulting.com/en/posts/20240618-valgrind-and-massif.html">Read more…</a> (1 min remaining to read)</p></div>freerdpmassifvalgrindhttps://www.hardening-consulting.com/en/posts/20240618-valgrind-and-massif.htmlTue, 18 Jun 2024 05:08:00 GMT