[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-dev] question: memory usage/allocation profiling of Gnash

From: Hong Yu
Subject: Re: [Gnash-dev] question: memory usage/allocation profiling of Gnash
Date: Tue, 09 Dec 2008 14:32:53 +0800
User-agent: Thunderbird (X11/20081125)

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:

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.


Gnash-dev mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]