Johannes Sixt writes:
>> +static void restore_sigpipe_to_default(void)
>> +{
>> +sigset_t unblock;
>> +
>> +sigemptyset(&unblock);
>> +sigaddset(&unblock, SIGPIPE);
>> +sigprocmask(SIG_UNBLOCK, &unblock, NULL);
>> +signal(SIGPIPE, SIG_DFL);
>> +}
>
> This does not build on Min
Am 18.09.2014 um 18:57 schrieb Patrick Reynolds:
> Blocked and ignored signals -- but not caught signals -- are inherited
> across exec. Some callers with sloppy signal-handling behavior can call
> git with SIGPIPE blocked or ignored, even non-deterministically. When
> SIGPIPE is blocked or ignor
Today I learned that software can be constipated.
On Thu, Sep 18, 2014 at 12:35 PM, Junio C Hamano wrote:
> Thanks!
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majord
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Blocked and ignored signals -- but not caught signals -- are inherited
across exec. Some callers with sloppy signal-handling behavior can call
git with SIGPIPE blocked or ignored, even non-deterministically. When
SIGPIPE is blocked or ignored, several git commands can run indefinitely,
ignoring E
5 matches
Mail list logo