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?
_______________________________________________
Libav-user mailing list
[email protected]
http://ffmpeg.org/mailman/listinfo/libav-user

Reply via email to