On Tue Sep 2 13:01:10 2025 +0000, Jinoh Kang wrote:
This seems to solve the same problem as !4811, where I suggested using `raise(SIGQUIT)` instead of e.g., refactoring all uninterrupted sections. It was closed with the following comment:
From off-list conversation, this isn't going to be enough to solve the
general problem of thread state becoming inconsistent when killed while in a syscall, probably mostly because of win32u problems. This needs more thought. @zfigura Could you elaborate on what the problem was? Since we now have a (more or less) reliably reproducible case, do you think it's okay to proceed with this MR (or !4811) even if it's not a complete solution?
FWIW, either MR appears to solve the *specific* case where a thread is killed due to broken server pipe, if not all syscalls.