Hi, I am using libumem to find leaks in a software. I am using ::findleaks -d to get the leaked buffers. I am getting output like,
BYTES LEAKED VMEM_SEG CALLER 8192 113 e78f4000 MMAP 8192 1 f8a44000 MMAP 32768 1 f87e4000 MMAP 16384 1 f82c4000 MMAP 16384 1 f7dc4000 MMAP 24576 1 f78e4000 MMAP 16384 1 f7164000 MMAP 32768 1 f6724000 MMAP 24576 1 f5864000 MMAP 32768 1 f5364000 MMAP 24576 1 f4e64000 MMAP 24576 1 f4bc4000 MMAP 16384 1 f4944000 MMAP 16384 1 f4904000 MMAP 8192 1 f4826000 MMAP 24576 1 f4806000 MMAP I am not able to interpret this information, can you please help me to locate the buffers those are leaking and also what is the significance of MMAP over here. I tried using ::walk vmem it gives same result for all addresses listed above, and ::bufctl_audit applied on this list gives same stack each time and that is also an incomplete stack. #2 When i load core file using mdb I get errors like, mdb: core file data for mapping at f2de4000 not saved: Unknown error mdb: core file data for mapping at f3364000 not saved: Unknown error mdb: core file data for mapping at f4164000 not saved: Unknown error Does it mean the core file is corrupt. Regards, Ajay -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/mdb-discuss/attachments/20090325/b613d6cd/attachment.html>
