ocaml/testsuite/tests/unwind
Xavier Leroy 8b6241c64c Skip tests/unwind on iOS / macOS ARM64, continued
Follow-up to 482b7feb3
2020-07-31 09:29:43 +02:00
..
README
check-linker-version.sh Tests for -stop-after scheduling 2019-10-30 19:05:23 +00:00
driver.ml Skip tests/unwind on iOS / macOS ARM64, continued 2020-07-31 09:29:43 +02:00
mylib.ml clean up whitespace and cut long lines 2016-02-17 13:36:27 +01:00
mylib.mli clean up whitespace and cut long lines 2016-02-17 13:36:27 +01:00
stack_walker.c test/unwind: exit with nonzero error code in case of failure 2020-07-28 10:27:07 +02:00

README

This test case is motivated by the fact that on OS X, external functions may
cause stack walks into the OCaml-generated stack frames. In particular, the
Objective-C runtime does so in function objc_addExceptionHandler. This function
is invoked from Cocoa. Errors in the stack unwinding info generated by OCaml
can cause random crashes. This test case checks that, for at least one OCaml
program, correct unwind info is generated such that the platform's unwinder
(called libunwind) correctly walks the stack up to the main function. OCaml
used to generate incorrect stack unwinding information for this program. See
PR#7118, PR#7120.