For printing out a chart kcachegrind will do the work as a front-end for callgrind which is part of the valgrind suite, long story short 'apt-get install kcachegrind'. ;)

//Markus

Rob Savoye wrote:
strk wrote:
Well, if we're taking too much memory we can't really tell
when we'll going to run out of it. I guess a proper approach
would be producing a diagram of where most memory goes,

  While mudflap won't print out a chart, it will tell you about every
access to see if there is a problem. Often I've seen bugs that trash the
stack create various weird errors, hiding the original problem. I also
have some code that instruments the malloc buffers in the kernel, which
can also be useful at times like this.

        - rob -


_______________________________________________
Gnash-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnash-dev

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Gnash-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnash-dev

Reply via email to