Cody Permann <[email protected]> writes: > Yeah, I guess I need to spend more time with Massif. I tried it last week > for the first time as well and was overwhelmed by the amount of output. > From what I've seen just scanning over the output is a detailed log of > when and how much memory is used. Is there a way to flip that tree > upside-down to see what structures hold onto memory? That would be > useful...
How would you identify those structures? PETSc can capture the stack (in debug mode) or the function (debug or optimized) where things are allocated, as well as the Stage (PETSc profiling). Massif is more complete, of course. ------------------------------------------------------------------------------ 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
