[FFmpeg-devel] [PATCH] Workaround to build ffmpeg on MacOs 10.15

[Michael Niedermayer]

On Sat, Jan 04, 2020 at 12:06:55AM +0100, Henrik Gramner wrote:
> On Fri, Jan 3, 2020 at 7:37 PM Moritz Barsnick <barsnick at gmx.net> wrote:
> > On Fri, Jan 03, 2020 at 11:05:25 +0100, Timo Rothenpieler wrote:
> > > I think this was discussed on this list in the past.
> > > Not sure what the conclusion was, but I think an unconditional flag like
> > > this being added wasn't all that well received.
> >
> > Yes, discussed in this thread in November:
> > http://ffmpeg.org/pipermail/ffmpeg-devel/2019-November/253193.html
> 
> Lmao "security feature". Just disable that flag and call it a day, it
> adds nothing of value (unless you consider crashing to be a "security
> feature"?).

I dont know how effective this is or what exactly this option does, i
couldnt find documentation for it quickly what it does in clang on macosx.
google keeps pointing to gcc 
but

a crash is better than arbitrary code execution, which IIUC is the idea
here, if the stack of a thread grows too much, crash instead of overwriting 
something that comes after it.
Not crashing when the stack overlapps another threads stack or heap is
unlikely to be better.

That said, thats when things work, IIUC theres some kind of bug in the
apple compiler.
If that is true the workaround of disablng the flag should only be
enabled when a affected compiler is used

Thanks

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

it is not once nor twice but times without number that the same ideas make
their appearance in the world. -- Aristotle
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20200104/3a311227/attachment.sig>