You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to small stack size of worker threads under macOS (512kb), LEDAKEM52LT emits a BUS ERROR (access violations -Exception: EXC_BAD_ACCESS (code=1, address=0x70000292c4c8) ) when attempted to be run in a non-main (worker) thread under macOS. The first culprit is
where the array gamma seems to have 609068 bytes, more than can be stored on the stack of a single non-main thread in macOS (512kb). Allocating gamma on the heap still doesn't solve the problem, other violations of the same sort keep appearing (I didn't have time to go over the rest). So we should think whether we want to keep the code as is, or document that it shouldn't be run on a thread under macOS, or change it.
The text was updated successfully, but these errors were encountered:
vsoftco
changed the title
LEDAKEM52LT cannot be run in a worker thread on macOS
LedaKemLT52 cannot be run in a worker thread on macOS
Feb 7, 2020
@dstebila Definitely more than 1 place. I tried changing the first stack allocation, and got into another issue of the same flavour down the line. I'll look into it when I get some time. Hopefully not dozens and dozens and places we'd need to change.
Due to small stack size of worker threads under macOS (512kb), LEDAKEM52LT emits a BUS ERROR (access violations -Exception: EXC_BAD_ACCESS (code=1, address=0x70000292c4c8) ) when attempted to be run in a non-main (worker) thread under macOS. The first culprit is
liboqs/src/kem/ledacrypt/pqclean_ledakemlt52_leaktime/dfr_test.c
Line 13 in fb45816
where the array
gamma
seems to have 609068 bytes, more than can be stored on the stack of a single non-main thread in macOS (512kb). Allocatinggamma
on the heap still doesn't solve the problem, other violations of the same sort keep appearing (I didn't have time to go over the rest). So we should think whether we want to keep the code as is, or document that it shouldn't be run on a thread under macOS, or change it.The text was updated successfully, but these errors were encountered: