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
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.
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: