* JINMEI Tatuya / 神明達哉: > Then the named process will eventually abort itself with a core dump > due to malloc failure. Please show us the stack trace at that point. > Hopefully it will reveal the malloc call that keeps consuming memory.
I've successfully used a backtrace()-instrumented malloc() to track down difficult memory leaks. backtrace() is necessary because it allows you to see past malloc() wrappers. (backtrace() seems to be part of libexecinfo on FreeBSD.) _______________________________________________ freebsd-performance@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-performance To unsubscribe, send any mail to "[EMAIL PROTECTED]"
