Carl Eugen Hoyos <[email protected]> added the comment:
I would like to repeat that this kind of bug-report is _very_ rude and definitely NOT welcome! (That is also true if it's a patch since the patch guidelines clearly ask for explanations.) valgrind ./ffmpeg_g -i no.png ==5489== Memcheck, a memory error detector ==5489== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==5489== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info ==5489== Command: ./ffmpeg_g -i no.png ==5489== FFmpeg version SVN-r24460, Copyright (c) 2000-2010 the FFmpeg developers built on Jul 26 2010 23:39:10 with gcc 4.4.4 configuration: cc='/usr/local/gcc-4.4.4/bin/gcc -m32' libavutil 50.23. 0 / 50.23. 0 libavcore 0. 0. 0 / 0. 0. 0 libavcodec 52.84. 0 / 52.84. 0 libavformat 52.76. 0 / 52.76. 0 libavdevice 52. 2. 0 / 52. 2. 0 libavfilter 1.26. 1 / 1.26. 1 libswscale 0.11. 0 / 0.11. 0 no.png: No such file or directory ==5489== ==5489== HEAP SUMMARY: ==5489== in use at exit: 940 bytes in 1 blocks ==5489== total heap usage: 12 allocs, 11 frees, 44,291 bytes allocated ==5489== ==5489== LEAK SUMMARY: ==5489== definitely lost: 940 bytes in 1 blocks ==5489== indirectly lost: 0 bytes in 0 blocks ==5489== possibly lost: 0 bytes in 0 blocks ==5489== still reachable: 0 bytes in 0 blocks ==5489== suppressed: 0 bytes in 0 blocks ==5489== Rerun with --leak-check=full to see details of leaked memory ==5489== ==5489== For counts of detected and suppressed errors, rerun with: -v ==5489== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 3) ---------- status: new -> open substatus: needs_more_info -> reproduced type: patch -> bug ________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/issue2126> ________________________________________________
