Use mdb in Solaris to check for Memory leakage

Perform Step 1: UMEM_DEBUG = default UMEM_LOGGING = transaction LD_PRELOAD = libumem. so.1. /spAgent & www.2cto.com Step 2:-bash-3.00 $ mdb-p 16546 // the above process obtains IDLoading modules: [ld. so.1 libumem. so.1 libc. so.1] Step 3:-bash-3.00 $ mdb-p 16546 Loading modules: [ld. so.1 libumem. so.1 libc. so.1]>: findleaks // find Memory leakage cache leaked bufctl CALLER00484008 11489 00a7f428 libstdc ++. so.6.0.3 '_ Znwj + 0x1c ------------- --------------------------------------------------------- Total 11489 buffers, 5147072 bytes www.2cto.com Step 4:> 00a7f428 :: bufctl_audit // view the call stack addr bufaddr timestamp thread cache lastlog contents a7f428 a85a00 2185ef54480864 47 484008 running 5dc 0 libumem using this memory address. so.1 'umem _ cache_alloc + 0x13c libumem. so.1 'umem _ alloc + 0x60 libumem. so.1 'malloc + 0x28 libstdc ++. so.6.0.3 '_ Znwj + 0x1c _ ZN6RXConn17HandleSMPPDel IverEPK7AIChunki + 0x510 _ ZN6RXConn10RecvThreadEv + 0x6c4 _ ZN6RXConn4RecvEPv + 0x20 libc. so.1 '_ lwp_start the above steps can basically locate Memory leakage in the xx function.