X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:content-type
	:content-transfer-encoding:mime-version; q=dns; s=default; b=ID1
	iuP6xuAtbhd6X9xbPDW/Mf7qgPdhxi/4JRdwJKXEd2fJ+t/riaI77M9q+ztPx/vq
	NvAFWpIAq4aLMzl9SXzDjI9oHVcDaGtYcA6aaKwN2ro3r4rmzSprHuSqq033TlWx
	YsSLE2rnBcpSgWrpmgApr1ZkcW3zRLi+PGo3TsNA=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:content-type
	:content-transfer-encoding:mime-version; s=default; bh=q8IZyPXng
	llCzbgSlNS17r+Hd1s=; b=GgWrebXuD6Vt7muBfaGEnypZsSIXmhIPKQIcGUygM
	4g5dRbSUW1xGVjDPeVuF6+OYjqzJH7X+A5tqoA0xanPHnIPzxkgqRvTak7UaZYrr
	WqpM8yRBB7RVPT3g0ZBVnG80717rHvbfUZlwZN3POF4g1X0meC81p6t5r71AZWW8
	2g=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	USA7109MR004.ACS-INC.COM
From:	"Nellis, Kenneth" <Kenneth DOT Nellis AT xerox DOT com>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	pipe handling errors
Date:	Mon, 14 Jul 2014 17:40:17 +0000
Message-ID:	<0D835E9B9CD07F40A48423F80D3B5A702E7EA6EB@USA7109MB022.na.xerox.net>
MIME-Version:	1.0
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id s6EHefrs007131

When running a bash pipeline using the latest 64-bit packages, 
I occasionally get output like the following:

1479561950 [waitproc] -bash 10000 sig_send: error sending signal 20, pipe handle 0x2710, nb 132, packsize 0, Win32 error 109

That one was the result of: strings <binary file> | grep <pattern> | sort | uniq -c

Here's a different one that I got twice when sending "strings" 
output to "grep" and once sending "strings" output to "wc -l":

605884587 [main] -bash 10000 sig_send: error sending signal -66, pipe handle 0x2710, nb 132, packsize 0, Win32 error 0

I haven't found them to be repeatable.

I just tried on 32-bit Cygwin and got the following twice in a row, 
but not a third time, so I suspect a race condition.

      1 [main] -bash 9528 sig_send: error sending signal -34, pipe handle 0x2538, nb 152, packsize 0, Win32 error 0
25098461 [main] -bash 9528 sig_send: error sending signal -34, pipe handle 0x2538, nb 152, packsize 0, Win32 error 0

The initial "1" on the first one looks interesting. 
This one also was: strings <binary file> | grep <pattern>

The common element in all these examples was generating the pipeline data
with "strings". I don't recall whether strings was always involved or not.

Not a big concern because the generated output looks correct, 
but a tad annoying. Thought it worth reporting.

FWIW, on 64-bit:
Cygwin64> uname -a
CYGWIN_NT-6.1 COR900GFY5 1.7.30(0.272/5/3) 2014-05-23 10:36 x86_64 Cygwin
Cygwin64> cygcheck -f `which strings`
binutils-2.24.51-4
Cygwin64>

On 32-bit:
Cygwin32> uname -a
CYGWIN_NT-6.1-WOW64 COR900GFY5 1.7.30(0.272/5/3) 2014-05-23 10:36 i686 Cygwin
Cygwin32> cygcheck -f `which strings`
binutils-2.24.51-4
Cygwin32>

--Ken Nellis

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

- Raw text -