New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
catch_break does not always catch break #3747
Comments
Comment author: administrator
This is because signal handling has to be synchronized by the OCaml runtime: The solution would be for the compiler to insert a test in every loop, but
In this case, the signal is not caught, but the OS kills the process directly. -- Damien |
Comment author: administrator Damien, On 8/10/05, Damien Doligez caml-bugs@pauillac.inria.fr wrote:
|
Comment author: administrator Issue is documented in ocamlopt chapter of ref. man. Feature wish: better |
Comment author: @mshinwell I think such better polling for signals might arrive with multicore, but I don't remember the details. |
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
This is a known problem with the current implementation of safe points that will be addressed by the multicore work. Given that, I don't think this old issue needs to remain open. |
Reopened because this is still an issue. There's some discussion about a potential fix in the multicore repo at ocaml-multicore/ocaml-multicore#187. |
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
Fixed by the "safepoints" PR #10039. |
Original bug ID: 3747
Reporter: administrator
Status: acknowledged
Resolution: open
Priority: normal
Severity: feature
Target version: later
Category: runtime system and C interface
Bug description
Full_Name: Henri
Version: 3.08.2
OS: linux
Submission from: aorleans-104-1-15-86.w80-11.abo.wanadoo.fr (80.11.35.86)
The following program never catches Ctrl+C in a terminal and loops forever.
The following program works as expected though!
The following program does not catch break of course, but exits properly when
Ctrl+C is pressed in the same environment.
The text was updated successfully, but these errors were encountered: