Hello,
Valgrind has been a good tool to study heap memory during program's
execution on Linux. How can we study and profile other part(s) of
dynamic memory during application's run, e.g., the stack usage belonging
to Gnash's run ? Anyone be interested to give suggestions? Thanks!
Best regards,
Hong Yu
strk wrote:
On Fri, Nov 07, 2008 at 12:57:32PM +0800, Hong Yu wrote:
Anyone would like to suggest how to
better utilize the valgrind tool, or, some linux memory profiling tool
better than valgrind? Thanks!
Valgrind is what I'd use. Try reading more about how to read
the output.
--strk;
_______________________________________________
Gnash-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnash-dev
_______________________________________________
Gnash-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnash-dev
