[FFmpeg-trac] #8073(undetermined:new): Segfault on macOS 10.15 "Catalina": stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT); libdyld.dylib`stack_not_16_byte_aligned_error

[FFmpeg]

#8073: Segfault on macOS 10.15 "Catalina": stop reason = EXC_BAD_ACCESS
(code=EXC_I386_GPFLT); libdyld.dylib`stack_not_16_byte_aligned_error
-------------------------------------+-------------------------------------
             Reporter:  skyzyx       |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  git-master   |               Resolution:
             Keywords:  osx          |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by zwaldowski):

 It seems the 10.15 toolchain turns on "-fstack-check" by default for
 Clang, like some Linux distributions do. You can see that
 [https://developer.apple.com/documentation/xcode_release_notes/xcode_11_beta_7_release_notes#3319458
 here]:

 {{{
 Stack checking is on by default on all platforms to prevent memory
 corruptions. (25859140)
 }}}

 Some discussion [https://github.com/jedisct1/libsodium/issues/848 here]
 traces it back to AVX, although turning off AVX ("--disable-avx") didn't
 seem to help building FFMPEG. (Nor, as skyzyx saw above, did turning off
 ASM entirely.)

 Accordingly, adding "-fno-stack-check" to "CFLAGS" - f.ex., by '--extra-
 cflags="-fno-stack-check"' when configuring works around the problem and
 builds a functioning FFMPEG.

 Don't quite know what that means for us. I imagine having stack checking
 on is desirable, but there's at least a workaround while the source is
 further investigated.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/8073#comment:12>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker