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
Original bug ID: 6489 Reporter: Richard Jones Assigned to:@mshinwell Status: closed (set by @xavierleroy on 2015-12-11T18:28:12Z) Resolution: fixed Priority: normal Severity: crash Version: 4.02.0+beta1 / +rc1 Fixed in version: 4.02.0+dev Category: back end (clambda to assembly)
Well, that's not quite true. All of the caml_callback* functions cause heap corruption. If you call Gc.compact () after any of them, then it will segfault. Only caml_callback2 segfaults on its own without any help.
Original bug ID: 6489
Reporter: Richard Jones
Assigned to: @mshinwell
Status: closed (set by @xavierleroy on 2015-12-11T18:28:12Z)
Resolution: fixed
Priority: normal
Severity: crash
Version: 4.02.0+beta1 / +rc1
Fixed in version: 4.02.0+dev
Category: back end (clambda to assembly)
Bug description
caml_callback2 segfaults when called, on aarch64.
Steps to reproduce
Compile the attached program using:
ocamlopt.opt callback.c callback_ml.ml -o callback
Then run it using:
./callback
The output is:
$ ./callback
f1 (100)
Segmentation fault
Note that caml_callback and caml_callback3 are fine, it's just caml_callback2 which fails.
File attachments
The text was updated successfully, but these errors were encountered: