I am developing a 64-bit C++ application on 64-bit CentOS 5.8 using the standard CentOS packages (gcc 4.4.6, not 4.1.2). It has been compiled with debug information. When I try profiling it with massif I always get the following in the massif.out.XXXX file using the command 'valgrind --tool=massif ./MyProg':
********** Begin massif.out.XXXX ********** desc: (none) cmd: ./MyProg time_unit: i #----------- snapshot=0 #----------- time=0 mem_heap_B=0 mem_heap_extra_B=0 mem_stacks_B=0 heap_tree=empty ********** End massif.out.XXXX ********** I have tried various combinations of options to massif with no change in the results. Since CentOS is using valgrind 3.5.0 I even tried downloading and compiling 3.8.1, but that produced the same results as well. I finally ended up trying 'valgrind --tool=massif ls -l' and it appeared to work properly (i.e. it produced multiple snapshots that had non-zero memory use). I have tried every combination of search keywords I can think of on Google and can't find any reports of similar problems. Does anyone have any idea what I am doing wrong? I am new to valgrind so I'm sure it is something simple that I have missed. It's probably not relevant, but just in case, I have been able to run memcheck against my program without any problems. I have not tried any of the other valgrind tools. Thanks, Tyson ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
