[Libav-user] stubborn valgrind issue

Brian Lewis brian at lorf.org
Thu Aug 1 19:55:40 CEST 2013

The very same test case test.c, when compiled against libraries from
ffmpeg 2.0, doesn't produce any invalid-read or
use-of-uninitialized-memory errors in valgrind. Can someone please
confirm that this makes sense? Maybe valgrind cleanliness was not a big
concern before?

More information about the Libav-user mailing list