Added:<br><br>  <a href="http://public.kitware.com/Wiki/TubeTK/Development/DevelopersGuide#Memory_Leaks">http://public.kitware.com/Wiki/TubeTK/Development/DevelopersGuide#Memory_Leaks</a><br><br>Thanks,<br>Matt<br><br><div class="gmail_quote">
On Sun, Jul 15, 2012 at 2:46 PM, Stephen Aylward <span dir="ltr"><<a href="mailto:stephen.aylward@kitware.com" target="_blank">stephen.aylward@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>Hi</p>
<p>This is great!  Please add this info to the wiki.</p>
<p>Thanks,<br>
S</p>
<div class="gmail_quote"><div><div class="h5">On Jul 5, 2012 5:23 PM, "Matt McCormick" <<a href="mailto:matt.mccormick@kitware.com" target="_blank">matt.mccormick@kitware.com</a>> wrote:<br type="attribution">
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Hi,<br><br>For effective valgrind-detected memory leak debugging, I have added scripts to the source tree.<br><br>  ./TubeTK/Utilities/Valgrind/runValgrind.sh -h<br><br>will show usage, but essentially install valgrind and xsltproc, then execute the runValgrind.sh script from TubeTK-Build with arguments such as "-R leakyTubeTestName".<br>


<br>It produces a summary and readable html output.<br><br>Happy hacking,<br>Matt<br>
<br></div></div>_______________________________________________<br>
Tubetk-developers mailing list<br>
<a href="mailto:Tubetk-developers@tubetk.org" target="_blank">Tubetk-developers@tubetk.org</a><br>
<a href="http://public.kitware.com/cgi-bin/mailman/listinfo/tubetk-developers" target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/tubetk-developers</a><br>
<br></blockquote></div>
</blockquote></div><br>