[FFmpeg-devel] Longevity Test Report

Alexander Strange astrange
Wed Feb 4 20:00:04 CET 2009

On Feb 4, 2009, at 6:22 AM, Robert Swain wrote:

> 2009/2/4 Reimar D?ffinger <Reimar.Doeffinger at stud.uni-karlsruhe.de>:
>> On Wed, Feb 04, 2009 at 12:00:53PM +0100, Benjamin Larsson wrote:
>>> My suggestion to find these kind of problems is to wrap av_malloc  
>>> in a
>>> macro that expands av_malloc to  
>>> av_leak_malloc(size,__FILE__,__LINE).
>> There are more than enough tools that do that already, only that most
>> suck. Please spend your efforts on fixing/improving those general
>> solutions instead implementing you own and very limited version.
>> Also the issue is not really a leak otherwise valgrind would probably
>> work fine (even if a little slow, and not on Windows).
> Nor Mac OS X.
> Regards,
> Rob

The experimental valgrind port works fine: http://www.sealiesoftware.com/valgrind/

and OS X already comes with 'leaks' and 'malloc_history' anyway.  
Nobody seems interested in backtraces that work with -fomit-frame- 
pointer, though, even though it should be possible using DWARF.

More information about the ffmpeg-devel mailing list