On 04.01.2020 14:37, Michael Niedermayer wrote:
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
This seems to be a known bug for quite a while now, why did it not get
fixed in the compiler yet?
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
