Yes, we have found valgrind can help detect more memory problems than leaks.
I am reading the trunk source. About the '*.m4' files under the
directory 'macros/', are they part of the development source, or can
they be auto-generated ? Thanks.
Best regards,
Hong Yu
strk wrote:
On Wed, Nov 26, 2008 at 05:22:22PM +0800, Hong Yu wrote:
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!
Valgrind should also do stack memory profiling.
--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
