"C. Bergstr?m" writes: > James Carlson wrote: > > "C. Bergstr?m" writes: > > > >> I'm 99% certain I've caused this, but if someone can give some pointers > >> on how to debug it that would be most appreciated. Someone suggested > >> libumem, but I'm pretty green in this field and > >> > > > > Use mdb and "::findleaks -d" will show you where the leaked buffers > > were allocated. > > > First thing I tried before I sent the email and got.. > > mdb - seed/core > Loading modules: [ libc.so.1 ld.so.1 ] > > ::findleaks > mdb: invalid command '::findleaks': unknown dcmd name
Oh ... you need to link with libumem first, or use LD_PRELOAD to force the use of that library rather than the allocators in libc. env LD_PRELOAD=libumem.so.1 UMEM_DEBUG=default ... See umem_debug(3MALLOC) for more information. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
