[FFmpeg-user] What is Segmentation fault: 11 ?

Nomis101 🐝 Nomis101 at web.de
Wed Aug 24 00:44:52 EEST 2016

Am 23.08.16 um 21:11 schrieb Moritz Barsnick:
> Go into the build directory, and launch your ffmpeg command as:
> $ gdb --args ./ffmpeg_g -i foo.mp4
I did this. First, I had to install gdb via Macports, because it gets
not installed anymore with Apple Developer Tools. But I think the output
is not helpful and unrelated:

/$ ggdb --args ./ffmpeg_g -i /Users/Downloads/Test.mp4 //
//GNU gdb (GDB) 7.9.1//
//Copyright (C) 2015 Free Software Foundation, Inc.//
//License GPLv3+: GNU GPL version 3 or later
//This is free software: you are free to change and redistribute it.//
//There is NO WARRANTY, to the extent permitted by law.  Type "show
//and "show warranty" for details.//
//This GDB was configured as "x86_64-apple-darwin16.0.0".//
//Type "show configuration" for configuration details.//
//For bug reporting instructions, please see://
//Find the GDB manual and other documentation resources online at://
//For help, type "help".//
//Type "apropos word" to search for commands related to "word"...//
//Reading symbols from ./ffmpeg_g...//
//warning: `/tmp/lto.o': can't open to read symbols: No such file or
//(no debugging symbols found)...done.//
//(gdb) run//
//Starting program: /Volumes/Developer/ffmpeg-3.1.2/ffmpeg_g -i
//Unable to find Mach task port for process-id 691: (os/kern) failure
// (please check gdb is codesigned - see taskgated(8))//

Am 23.08.16 um 21:48 schrieb Carl Eugen Hoyos:
> You start with removing everything between --enable-avisynth and
> --enable-openssl and confirm that the crash still happens.
> Then you remove --enable-lto (or test with --enable-lto only)
> because this is the most time-consuming of your options.
OK, I did lots of different builds now. And the suspicious option is
--enable-lto. I can remove all other options, no difference. But if I
remove --enable-lto, than I do not see the Segmentation fault issue anymore.

More information about the ffmpeg-user mailing list