15 May
2025
15 May
'25
4 p.m.
On Thu May 15 15:18:59 2025 +0000, eric pouech wrote:
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?
Thanks for your patience, I rearranged the test to put the intermediate between both ctrl-c tests. Unfortunately I can't now tell which process 0x61c was.
Trying to continue to test.