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: 458 Reporter: administrator Status: closed Resolution: not a bug Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
In general, POSIX standard signals have two numbers: the OS-imposed number
(e.g. 14 for sigalrm under Linux) and the conventional, OS-independent
number found in Sys.sigalrm. So, it's wise not to assume your handler
will be given one of these numbers reliably. Still, if you must:
Before 3.01, the handler received the OS-dependent number.
In 3.01, the handler receives the conventional number with ocamlc, and
the OS-dependent number with ocamlopt (the modification wasn't
reported correctly to the ocamlopt runtime system).
In the forthcoming 3.02, the conventional number will be reported for all.
Original bug ID: 458
Reporter: administrator
Status: closed
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Eijiro Sumii
Version: 3.01
OS: Linux 2.2.17 (Debian/potato)
Submission from: 210.238.31.142.tcn-catv.ne.jp (210.238.31.142)
Isn't this a problm of signal handling in ocaml-3.01?
let _ =
Sys.set_signal Sys.sigalrm (Sys.Signal_handle signal_handler);
ignore (Unix.alarm 1);
Unix.sleep max_int
The "Changes" file says:
signal number rather than the raw system signal number whenever possible.
Probably the problem above is related to this change?
The text was updated successfully, but these errors were encountered: