On Thu, May 30, 2013 at 10:58 AM, Kirk, Benjamin (JSC-EG311) < [email protected]> wrote:
> > This is basically what I do, but I use valgrind's massif tool: > http://valgrind.org/docs/manual/ms-manual.html > > This wraps malloc and reports exactly what memory is used by what data > structures. There is a significant runtime penalty for it, but it is as > precise as you could hope to get. > > Apple's Xcode's 'Instruments' has another tool which does a similar job > but a lot faster. Basically, compile your app with CXXFLAGS="-g" to make > sure debugging symbols are in optimized mode, and run it through > Instruments using the memory profiling tool. > > -Ben > Thanks for pointer to Xcode, Ben. I have used it a lot for runtime profiling, and identifying memory leaks, but hadn't thought of it for memory profiling as well. Will give it a shot. Manav ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
