Michael Niedermayer <[email protected]> added the comment:
On Tue, Jun 30, 2009 at 06:28:54PM +0000, WD wrote:
> Attached is a zip file with multiple (73) files that cause ffmpeg to crash.
> The
> crashers are in a subset of various codecs. Included with each
> codec/directory are:
> 1) The seed/good file
> 2) Variations of the file that cause crashes (basename.x.y)
> 3) GDB output for the crashing testcases
stuff like
decode_frame (avctx=0x8a25700, data=0xbfffe138,
data_size=0xbfffe318, avpkt=0xbfffe240) at /usr/include/bits/string3.h:52
yeah it surely is in /usr/include/bits/string3.h
or
#1 0x084acdd9 in av_rescale_rnd (a=0, b=0, c=0, rnd=AV_ROUND_NEAR_INF)
#2 0x084ace2f in av_rescale (a=1, b=1, c=1) at libavutil/mathematics.c:111
they obviously match and 1 != 0
or
i = <value optimized out>
IMHO, if you do such large scale testing, it would be nice if it was actually
producing correct and useable output, as is, for some cases i cant even guess
what happened, like:
smclockmpeg1.avi.1.0
it doesnt point to any file from ffmpeg and valgrinds backtraces are pretty
terse ...
maybe you should recompile without -fomit-frame-pointer and without any
inlining and minimum optimizations and rerun these tests (x86 directory
might need more agressive flags to compile)
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The bravest are surely those who have the clearest vision
of what is before them, glory and danger alike, and yet
notwithstanding go out to meet it. -- Thucydides
_____________________________________________________
FFmpeg issue tracker <[email protected]>
<https://roundup.ffmpeg.org/roundup/ffmpeg/issue1240>
_____________________________________________________
