Hello,

Michael Kelly, le mar. 17 mars 2026 21:13:53 +0000, a ecrit:
> I don't have enough knowledge of this to make conclusions without further
> input. My guess would be that the assignment of EINTR on the client side in
> this instance is wrong.

Indeed. As I would understand it, the interrupt call should make the
server carefully stop its operation, and have the opportunity to return
either EINTR or a short read/write. Then the client should be able to
receive that and return it.

Claude's suggestion of not calling abort_all_rpcs() in suspend() is just
papering over the real issue, which would definitely happen with signal
handling, anyway, so better really fix the issue than avoid it.
(and no, this issue cannot explain the corrupted haskell symbol tables,
since it's not about a repeated piece of data, the binary would be
completely bogus otherwise)

Samuel

Reply via email to