Hey,<div>I&#39;ve been using gdb, linux and mt programming for a good year or two now in a professional</div><div>setting and I have following advice:</div><div>1) Get a good logging framework. We use log4cxx but I think someone is working on </div>

<div>boost logging too. For some things you just need to be able to follow logging</div><div>2) Use valgrind often! It is usually 100% correct when it points to problems in your code but</div><div>might be incorrect when pointing out problems in libs.</div>
<div>3) Get a good testing framework like google gtest... which you then run under valgrind...</div>
<div>4) Configure your system to dump core.</div><div>We have tried hellgrind and found the output difficult to interpret and giving too much false</div><div>positives -- but on the other hand they might be disasters waiting too happen.</div>
<div>Greetz,</div><div>Immanuel</div>
<div><br></div><div><br><div class="gmail_quote">On Tue, Mar 8, 2011 at 1:24 PM, Harry Van Haaren <span dir="ltr">&lt;<a href="mailto:harryhaaren@gmail.com" target="_blank">harryhaaren@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey,<br><br>Thanks for the &quot;thead apply all bt&quot; tip, gets me a bit more info.<br><br>As it happens I fixed the bug that cause this thread by mistake, it was a deadlock in GUI code.<br><br>I&#39;ve looked into valgrind and helgrind, getting lots of output... don&#39;t really know how to use it yet.<br>


Tutorials and man will sort me out when I get time...<br><br>Thanks, -Harry<br>
<br>_______________________________________________<br>
Linux-audio-dev mailing list<br>
<a href="mailto:Linux-audio-dev@lists.linuxaudio.org" target="_blank">Linux-audio-dev@lists.linuxaudio.org</a><br>
<a href="http://lists.linuxaudio.org/listinfo/linux-audio-dev" target="_blank">http://lists.linuxaudio.org/listinfo/linux-audio-dev</a><br>
<br></blockquote></div><br></div>