Ah, more mdb/libumem tips:
::findleaks will show you who allocated the memory, but that
mightn't be very helpful. Luckily, libumem records a stack trace at
each allocation, use BUFFER$<bufctl_audit to print that out.
Eg, to display the top 5 'leakers' and look at stack traces for them:
> ::findleaks ! sort -k 2 -n | tail -5
000c4c88 12 00284ca8 myallocator+4
000c4508 15 003b4708 myallocator+4
000c4508 869 003ea5a0 myallocator+4
000c4508 885 003b4780 myallocator+4
<lots of useful info, including thread id, last alloc + the important
stack trace of call path leading to the allocation..>
Paul Jakma paul at clubi.iepaul at jakma.org Key ID: 64A2FF6A
Kissing a fish is like smoking a bicycle.
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!