On Thu May 15 14:05:20 2025 +0000, Bernhard Übelacker wrote:
Sorry, I had not completely read the test an failed to see the parent is already using SetConsoleCtrlC. I pushed another version which I hope gets near your second option. But with it I get also sometimes two of these lines: `061c:0628:fixme:console:default_ctrl_handler Terminating process 61c on event 0` with a failure from _run_timeout_ctrlc/"Expected exitcode %ld, got %lx\n" with exitcode_expected=1.
didn't try it (and my first post wasn't 100% clear, sorry about that), but I think we need an intermediate process for each one of the two tests... basically we don't control when the ctrl-c event is dispatched, so as soon as GenerateConsoleCtrlEvent is called, re-enabling ctrl-c opens a window of risk if the event isn't dispatched soon enough
in the error you see, did you discriminate which process is 0x61c?