I found this while debugging a memory access error crash during stack unwinding when handling parse failure exception (which I'm still investigating, still not sure if that's on my end or Faust's).
Running with -fsanitize=address gave:
==53040==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x00016b443df8 at pc 0x00010e10ca50 bp 0x00016b442c70 sp 0x00016b442420
READ of size 8 at 0x00016b443df8 thread T0
#0 0x10e10ca4c in __asan_memcpy+0x37c (libclang_rt.asan_osx_dynamic.dylib:arm64+0x50a4c)
#1 0x10fd9e33c in llvm_dynamic_dsp_factory_aux::initJIT(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>>&) llvm_dynamic_dsp_aux.cpp:348
#2 0x10fda5944 in createDSPFactoryFromSignals(std::__1::basic_string<char,
...
This looks like a simple min/max typo bug to me. (In my case, fOptLevel was 5.)
I found this while debugging a memory access error crash during stack unwinding when handling parse failure exception (which I'm still investigating, still not sure if that's on my end or Faust's).
Running with
-fsanitize=address
gave:This looks like a simple
min
/max
typo bug to me. (In my case,fOptLevel
was 5.)