title: Alternative to valgrind (memcheck) for finding leaks on linux?
body: <p>I have a linux x86 application that makes use of various third-party shared-object libraries. I suspect these libraries are leaking memory (since it can't possibly be <strong>my</strong> code ;-)</p>
  
  <p>I tried the trusty valgrind, but it died a horrible death because <a href="http://forums.ni.com/t5/Multifunction-DAQ/Does-anyone-try-to-use-valgrind-with-software-linked-against/m-p/1400674" rel="noreferrer">one of the third-party libraries is using an obscure x86 instruction</a> that <a href="https://bugs.kde.org/show_bug.cgi?id=260935" rel="noreferrer">valgrind doesn't implement</a>.</p>
  
  <p>I found <a href="https://stackoverflow.com/questions/1052145/g-multi-platform-memory-leak-detection-tool/2938813#2938813">a recommendation for DUMA</a> and gave it a try (using the LD_PRELOAD technique to bring DUMA in at run-time), but it aborted complaining about a free operation on memory that wasn't allocated via DUMA (almost certainly by some constructor of a static object in one of the previously mentioned third-party libraries).</p>
  
  <p>Are there other run-time-linkable (or otherwise not requiring a recompilation/relink) tools around that will work on linux?</p>