On Wed, 4 May 2005, Sean Ryan wrote:
> Essentially I'm looking for opinions on commercial or open source memory
> checker. It should support the following :
>> - run time detection / reporting of memory leak, heap corruption etc.
> The application is fairly large so shutting downing is time consuming
>> - support for dynamic shared object linking - basically dlopen / dlsym
>> - Ability to pinpoint to source file / line where leak occurred.
>>> I've already tried the following with no real success yet.
>> mpatrol - dreadfully slow, has no real time support (i.e. I must
> shutdown the application before it reports heap growth, corruption etc)
>> dmalloc - does not have fantastic support for shared objects or c++ name
> unmangling (strangely addr2line does not resolve addresses to source
> code locations even though symbols are absolutely built in)
>> I do have an old version of purify lying around here somewhere but I'm
> dammed if I can figure it out - any decent tutorials around anywhere.
You don't need to buy anything, man libumem.
libumem in leak-finding mode + mdb is excellent for finding memory
leaks, better than valgrind (lower overhead at least).
Paul Jakma paul at clubi.iepaul at jakma.org Key ID: 64A2FF6A
Save energy: Drive a smaller shell.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!