On Fri, Nov 21, 2008 at 03:40:04PM +0100, [EMAIL PROTECTED] wrote: > Hi Venkat, > > venkat wrote: > > Hi , > > I am new to the Dtrace . i have C++ application which have multiple > > modules . > > > > i want to test memoryleaks from entire project . i tested sample C++ > > programs > > > > with Dtrace , but here i am getting count of new and deletes . > > > > I want details of causes of memory leaks from application . can > > i get those from dtrace . please help me on this . other wise give me > > suggestion how can i approach apart from purifyplus. > > > Take a look at http://developers.sun.com/solaris/articles/dtrace_cc.html
You may also want to use libumem; it's a better tool for memory leak detection. Doing something like: % LD_PRELOAD=libumem.so \ UMEM_DEBUG=audit=30,maxverify=0,verbose \ ./my_program (the "30" in "audit=30" is how many stack frames to record) while it's running, you can do: % mdb -p pid Loading modules: [ ... ] > $G C++ symbol demangling enabled > ::findleaks -d That will report all leaked buffers, grouped by size and stack trace. You can do ":c" to continue the process, or "$q" to quit MDB. Cheers, - jonathan _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
