On Tue, Aug 30, 2005 at 05:40:30PM -0700, prasad wrote: > > On my Solaris 10 FCS, I backed out 117461-04 for now and ::findleaks works: > > > ::findleaks > BYTES LEAKED VMEM_SEG CALLER > 4194304 5 fd800000 MMAP > 131072 1 fe4d0000 MMAP > 262144 1 fe480000 MMAP > 524288 1 fe380000 MMAP > 1048576 1 fe200000 MMAP > > ------------------------------------------------------------------------ > Total 5 oversized leaks, 6160384 bytes
Those are leaked mmap(2) segments. Without using something like dtrace(1M) to track them, there's no good way to know how they are being allocated, since there's no userland information. Cheers, - jonathan -- Jonathan Adams, Solaris Kernel Development
