Vitor <[email protected]> added the comment:
Not necessarily a bug. Code like the following trigger such warnings:
{
char in[4];
in[0] = 0;
GetBitContext gb;
init_get_bits(&gb, in, 8);
printf("%d\n", get_bits(&gb, 1));
}
Note that this code is valid will always print "0", but valgrind will complain
because the bitstream reader use 32-bit ops for speed. Does the output (ie, the
raw decoded video) varies from one run to the other? Also try "valgrind
--malloc-fill=0xaa" or something like that to test if the output does indeed
depends on uninitialized mem.
________________________________________________
FFmpeg issue tracker <[email protected]>
<https://roundup.ffmpeg.org/issue2295>
________________________________________________
