diff options
| author | Bart Jacobs <bart.jacobs@cs.kuleuven.be> | 2016-01-18 10:49:55 +0100 |
|---|---|---|
| committer | Bart Jacobs <bart.jacobs@cs.kuleuven.be> | 2016-01-18 10:49:55 +0100 |
| commit | 08c04f68acbdbd60a168fa72cef1626b4e663a41 (patch) | |
| tree | fdde8db1486a0e43d77fd7159c40e2ac7c2eb992 /testsuite | |
| parent | 3ad96f425b0942fcf57cddbbed9106cea7518e87 (diff) | |
| download | ocaml-08c04f68acbdbd60a168fa72cef1626b4e663a41.tar.gz | |
Add README file motivating unwind test case
Diffstat (limited to 'testsuite')
| -rw-r--r-- | testsuite/tests/unwind/README | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/testsuite/tests/unwind/README b/testsuite/tests/unwind/README new file mode 100644 index 0000000000..ff467e25da --- /dev/null +++ b/testsuite/tests/unwind/README @@ -0,0 +1,9 @@ +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. |