On Sun, Jan 29, 2017 at 07:59:22PM +0000, Mark Thompson wrote: > The string codec name need not be as long as the value we are > comparing it to, so memcmp may make decisions derived from > uninitialised data that valgrind then complains about (though the > overall result of the function will always be the same). Use > strncmp instead, which will stop at the first zero byte and > therefore not encounter this issue. > --- > libavformat/mov.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-)
probably OK Diego _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
