git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH jk/push-client-deadlock-fix] Windows: add pthread_sigmask() that does nothing

From
Jeff King <peff@peff.net>
Date
May 3, 2016, 04:48 UTC
Message-ID
<20160503044845.GC32259@sigill.intra.peff.net>
In-Reply-To
<57265425.9050205@kdbg.org>
On Sun, May 01, 2016 at 09:08:21PM +0200, Johannes Sixt wrote:
Show 9 quoted lines
> A previous change introduced a call to pthread_sigmask() in order to block
> SIGPIPE in a thread. Since there are no signal facilities on Windows that
> are similar to POSIX signals, just ignore the request to block the signal.
> In the particular case, the effect of blocking SIGPIPE on POSIX is that
> write() calls return EPIPE when the reader closes the pipe. This is how
> write() behaves on Windows.
> 
> Signed-off-by: Johannes Sixt <j6t@kdbg.org>
> ---

Looks good to me based on our earlier discussion (but of course I have no platform to test it on).

-Peff
Previous: Johannes Sixt
Message 4 of 4 in “pthread_sigmask() on windows (wine actualy)”
  1. Duy NguyenMay 1, 2016
  2. Jeff KingMay 1, 2016
  3. Windows: add pthread_sigmask() that does nothingJohannes Sixt, May 1, 2016
  4. Jeff KingMay 3, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.