Vitor <[email protected]> added the comment: Baptiste Coudurier wrote: >> >> vi...@vitor:~$ valgrind --malloc-fill=0xff ../../../ffmpeg.milepost/ffmpeg_g >> -i >> v210_720p-partial.avi -pix_fmt yuv422p16be -an -f framecrc - >> [ identical valgrind output omitted ] >> 0, 0, 3686400, 0x654f4ce3 > > Is it possible to trace even further ? Like where the memory was allocated ?
No, I've never succeeded in getting a deeper backtrace with valgrind :( _____________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/roundup/ffmpeg/issue1465> _____________________________________________________
