This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/85132] ffmpeg runtime segfault with lto
- From: "manuel.lauss at googlemail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 31 Mar 2018 08:53:22 +0000
- Subject: [Bug lto/85132] ffmpeg runtime segfault with lto
- Auto-submitted: auto-generated
- References: <bug-85132-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85132
--- Comment #6 from Manuel Lauss <manuel.lauss at googlemail dot com> ---
(In reply to Martin Liška from comment #5)
> (In reply to Manuel Lauss from comment #4)
> > (In reply to Martin Liška from comment #3)
> > > (In reply to Manuel Lauss from comment #2)
> > > > This is the most minimal ffmpeg config that can trigger the segfault. The
> > > > interesting switch is "--enabled-hardcoded-tables". I use the "mpv" Player
> > > > with a standard mp4 video file to trigger it
> > > > (https://github.com/mpv-player/mpv/archive/v0.27.2.zip)
> > >
> > > Good. so we have minimal set of options for ffmpeg. Now please explain me
> > > how to build the MPV tool? Is it really needed? Can't one trigger that
> > > directly with ffmepg? Please upload somewhere the mp4 file so that I can
> > > reproduce it.
> >
> > The segfault happens during initialization of ffmpeg when mpv player starts.
> > I can also trigger it with firefox on e.g. youtube: it crashes the tab.
>
> Ok, so please download following sample video:
> http://techslides.com/demos/sample-videos/small.mp4
>
> And try to run ffmpeg to print info:
> ./ffmpeg -i small.mp4
>
> Does it also segfault?
Yes, same backtrace, same fault location.