Re: [PATCH] sigchain: recover from concurrent double-pops of the same signal
On Thu, Oct 29, 2026 at 04:03:18PM +0000, Phillip Wood wrote:
Show 8 quoted lines
>On 29/10/2026 14:15, ian4hu wrote:
>> I left SIGPIPE out precisely to keep the "upstream of a pipe
>> dies of SIGPIPE" behaviour that common-init.c restores. The set I
>> plan to block is SIGINT, SIGHUP, SIGTERM and SIGQUIT. If you
>> think SIGPIPE belongs in it too, I will add it.
>
>I think we want to block all signals when we create a thread, so that >all signals are handled by the main (initial) thread.
>
that wording again does not address the fact that sigpipe is different due to being thread-directed [1]. even if the outcome is identical, it needs to be reasoned about separately.
[1] https://stackoverflow.com/questions/21718311/when-multi-thread-program-receive-a-sigpipe-signal-because-send-which-thread-wo