Cyril <[email protected]> added the comment:
My configuration:
./configure --enable-shared --disable-avdevice --enable-ffplay
--enable-hwaccel=vaapi --enable-pthreads --disable-indevs
I've tried with -m32 and it's working (no valgrind uninitialized error).
Tried with amd64 build and the test file you said, got a different output:
LD_PRELOAD="libavcodec/libavcodec.so.52 libavfilter/libavfilter.so.1
libavformat/libavformat.so.52 libavutil/libavutil.so.50
libswscale/libswscale.so.0 libavcore/libavcore.so.0" valgrind
--track-origins=yes ./ffmpeg_g -i ./AUD_MW_E.264
==26396== Memcheck, a memory error detector
==26396== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==26396== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for
copyright info
==26396== Command: ./ffmpeg_g -i ./AUD_MW_E.264 -o a.jpg
==26396==
FFmpeg version SVN-r25350, Copyright (c) 2000-2010 the FFmpeg developers
built on Oct 14 2010 10:06:03 with gcc 4.4.5
configuration: --enable-shared --disable-avdevice --enable-ffplay
--enable-hwaccel=vaapi --enable-pthreads --disable-indevs
libavutil 50.32. 2 / 50.32. 2
libavcore 0. 9. 1 / 0. 9. 1
libavcodec 52.92. 0 / 52.92. 0
libavformat 52.79. 0 / 52.79. 0
libavfilter 1.48. 0 / 1.48. 0
libswscale 0.12. 0 / 0.12. 0
==26396== Conditional jump or move depends on uninitialised value(s)
==26396== at 0x4FD165D: ff_h264_find_frame_end (h264_parser.c:54)
==26396== by 0x4FD1958: h264_parse (h264_parser.c:262)
==26396== by 0x50BF168: av_parser_parse2 (parser.c:184)
==26396== by 0x5DA11C8: av_read_frame_internal (utils.c:1060)
==26396== by 0x5DA1E8A: av_find_stream_info (utils.c:2254)
==26396== by 0x407712: opt_input_file (ffmpeg.c:3240)
==26396== by 0x411977: parse_options (cmdutils.c:204)
==26396== by 0x40F11E: main (ffmpeg.c:4362)
==26396== Uninitialised value was created by a heap allocation
==26396== at 0x4C236B6: memalign (vg_replace_malloc.c:581)
==26396== by 0x4C2370F: posix_memalign (vg_replace_malloc.c:709)
==26396== by 0x5FE0197: av_malloc (mem.c:83)
==26396== by 0x4ECA7F4: av_new_packet (avpacket.c:52)
==26396== by 0x5D7A9B8: ff_raw_read_partial_packet (rawdec.c:79)
==26396== by 0x5D9F717: av_read_packet (utils.c:665)
==26396== by 0x5DA1038: av_read_frame_internal (utils.c:1105)
==26396== by 0x5DA1E8A: av_find_stream_info (utils.c:2254)
==26396== by 0x407712: opt_input_file (ffmpeg.c:3240)
==26396== by 0x411977: parse_options (cmdutils.c:204)
==26396== by 0x40F11E: main (ffmpeg.c:4362)
==26396==
[h264 @ 0x7452640] Estimating duration from bitrate, this may be inaccurate
Seems stream 0 codec frame rate differs from container frame rate: 50.00 (50/1)
-> 25.00 (50/2)
Input #0, h264, from './AUD_MW_E.264':
Duration: N/A, bitrate: N/A
Stream #0.0: Video: h264, yuv420p, 176x144, 25 fps, 25 tbr, 1200k tbn, 50
tbc
At least one output file must be specified
==26396==
==26396== HEAP SUMMARY:
==26396== in use at exit: 362,922 bytes in 221 blocks
==26396== total heap usage: 384 allocs, 163 frees, 1,058,371 bytes allocated
==26396==
==26396== LEAK SUMMARY:
==26396== definitely lost: 0 bytes in 0 blocks
==26396== indirectly lost: 0 bytes in 0 blocks
==26396== possibly lost: 0 bytes in 0 blocks
==26396== still reachable: 362,922 bytes in 221 blocks
==26396== suppressed: 0 bytes in 0 blocks
==26396== Rerun with --leak-check=full to see details of leaked memory
==26396==
==26396== For counts of detected and suppressed errors, rerun with: -v
==26396== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 2 from 2)
Please try with a .mp4 file containing a H264 video track, you'll get the exact
error I have (it's the av_find_stream_info function that's called through mp4
parser).
________________________________________________
FFmpeg issue tracker <[email protected]>
<https://roundup.ffmpeg.org/issue2295>
________________________________________________
