DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 158193858D39
Message-ID: <10838112-58af-4b53-baac-39ab849662a4@gmail.com>
Date: Mon, 6 May 2024 23:01:49 +0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: SIGALRM is not interrupting a blocking write to a pipe
To: cygwin AT cygwin DOT com
Content-Language: en-US
From: ilya Basin via Cygwin <cygwin AT cygwin DOT com>
Reply-To: ilya Basin <basinilya AT gmail DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Hi List!

I need your help with troubleshooting an issue with "pv": https://codeberg.org/a-j-wood/pv/issues/87

This app uses SIGALRM to interrupt a blocking write to STDOUT and read more data into the buffer.
On Linuxes write() returns 0 after the signal, but on Cygwin even though the signal handler is called, the write call does not return, at least when writing to a pipe.

In the user guide it says "All sockets are non-blocking under the hood to allow to interrupt blocking calls by POSIX signals". It doesn't mention pipes, but I think the pipes should also be non-blocking under the hood.

In main.c the use of O_NONBLOCK is commented with "this can cause problems with (broken) applications such as dd". If I uncomment it the app is able to detect that the pipe is ready for writing. Have you ever heard about O_NONBLOCK breaking dd?


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple