-
Notifications
You must be signed in to change notification settings - Fork 193
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
benchexec does not terminate when CTRL-c is pressed #874
Comments
Is the problem that BenchExec does not react to Ctrl+C at all, or just that it reacts delayed, i.e., terminates after the initial phase is finished and actual benchmarking would start? I suspect it is the latter, because if we retrieve Ctrl+C we set an internal flag and that should be checked at latest when benchmarking starts. So it would be a goal to reduce the delay somewhat, which would probably be possible by checking the mentioned flag at a few points during initialization. |
Yes, exactly. For large benchmark sets, the initial phase can last several minutes, and sometimes one wants to terminate the process. |
In the phase at the very beginning, when benchexec computes the the set of benchmark tasks, it does not react on CTRL-c.
The text was updated successfully, but these errors were encountered: