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
