Am Mo., 3. Juni 2019 um 17:14 Uhr schrieb Jason Duerstock <jason.duerst...@gmail.com>: > > Hello again Carl, > > Sorry it took so long to get back to you. I took another stab at > bootstrapping ffmpeg, and it seems like the bulk of the test errors revolve > around src/libavcodec/ituh263enc.c. Specifically: > > $ gdb ./ffmpeg --core=core.1559574121 > GNU gdb (Debian 8.2.50.20190222-1) 8.2.50.20190222-git > Copyright (C) 2019 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > Type "show copying" and "show warranty" for details. > This GDB was configured as "ia64-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>. > Find the GDB manual and other documentation resources online at: > <http://www.gnu.org/software/gdb/documentation/>. > > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from ./ffmpeg... > [New LWP 6314] > [New LWP 6317] > [New LWP 6318] > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/ia64-linux-gnu/libthread_db.so.1". > Failed to read a valid object file image from memory. > Core was generated by `/home/jason/ffmpeg-4.1.3/debian/standard/ffmpeg > -nostdin -nostats -y -cpuflags'. > Program terminated with signal SIGSEGV, Segmentation fault.
> #0 init_mv_penalty_and_fcode (s=0x20000008000f3880) at > src/libavcodec/ituh263enc.c:776 > 776 s->me.mv_penalty= mv_penalty; // FIXME exact table for MSMPEG4 & > H.263+ What surprises me a little is that this line is not part of init_mv_penalty_and_fcode(). Do you see the same crash if you add --disable-optimizations to configure? Carl Eugen
