2017-10-06 16:19 GMT+02:00 Aoife Fitzmaurice <[email protected]>: > >>Generally, a backtrace, disassembly and register dump are > required for crash reports (esp. if they are not easily reproducible).
> Thanks for your response! I changed the dimensions to 320x240 > and it worked as expected. Allow me to repeat my question that you cut: Does it crash because of oom, or for other reasons? I cannot answer that, you should be able to see if the memory consumption is moderate or huge. > It may just be that the files are too large. > > I was following the ffmpeg bug report documentation > (https://www.ffmpeg.org/bugreports.html) to try and get any additional > information on why the process crashed with the original file, but that > process didn't work either. > > Input: ifi-mac-pro:~ admin$ gdb ffmpeg Could it be that you should use "lldb" instead of gdb? In any case, only debugging "ffmpeg_g" helps, "ffmpeg" should not contain any debug symbols. Carl Eugen _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
