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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=ZcZlZu/DOa5gdBLoJeYtAYf5EMlWsNPTf4p6U45yJI7YzDh9G0FJW
	qn2eapcYyU9mJZpPmKnu54ATpkoMBTnyaFPJRkxZ2GV6fzc6auHo9EIgSZwYv3w3
	DM7oL6fOJ6/RVb6dIG1v7RalRK9B7AEOTbZuM0oKSM3j8WhMs6Nc6k=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=gp+s59FH7MgV+ghPssRDZznlO3U=; b=t3sxUaaBvWkbHgwM7S6gDE//BJUg
	FIxT6atBGvdcXWkHdRhysb5ytrVjgTbe7b8y1qjDko1BtRv3dP2/RdMEq2RFW/Wd
	Y/ND3BAGgVL8XXOfMV9Bt/tgPfXmZPWXcZ74L2QhN/Uqaoh6UdTjFPWGUR3FzLuH
	zRCUeLyuGa1HrgU=
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=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Tue, 15 Jul 2014 11:49:49 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: pipe handling errors
Message-ID:	<20140715094949.GJ10401@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<0D835E9B9CD07F40A48423F80D3B5A702E7EA6EB AT USA7109MB022 DOT na DOT xerox DOT net>
MIME-Version:	1.0
In-Reply-To:	<0D835E9B9CD07F40A48423F80D3B5A702E7EA6EB@USA7109MB022.na.xerox.net>
User-Agent:	Mutt/1.5.23 (2014-03-12)

--GLp9dJVi+aaipsRk
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jul 14 17:40, Nellis, Kenneth wrote:
> When running a bash pipeline using the latest 64-bit packages,=20
> I occasionally get output like the following:
>=20
> 1479561950 [waitproc] -bash 10000 sig_send: error sending signal 20, pipe=
 handle 0x2710, nb 132, packsize 0, Win32 error 109
>=20
> That one was the result of: strings <binary file> | grep <pattern> | sort=
 | uniq -c
>=20
> Here's a different one that I got twice when sending "strings"=20
> output to "grep" and once sending "strings" output to "wc -l":
>=20
> 605884587 [main] -bash 10000 sig_send: error sending signal -66, pipe han=
dle 0x2710, nb 132, packsize 0, Win32 error 0
>=20
> I haven't found them to be repeatable.
>=20
> I just tried on 32-bit Cygwin and got the following twice in a row,=20
> but not a third time, so I suspect a race condition.
>=20
>       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 handl=
e 0x2538, nb 152, packsize 0, Win32 error 0
>=20
> The initial "1" on the first one looks interesting.=20
> This one also was: strings <binary file> | grep <pattern>
>=20
> 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.
>=20
> Not a big concern because the generated output looks correct,=20
> but a tad annoying. Thought it worth reporting.
>=20
> 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>
>=20
> 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 Cy=
gwin
> Cygwin32> cygcheck -f `which strings`
> binutils-2.24.51-4
> Cygwin32>

I know that we got this message more often in the past, but I'm totally
unable to reproduce it these days.  I tried with 1.7.30 as well as the
latest snapshots.

I'm wondering if a pipe could be intercepted by a virus checker or
something like that.  Whatever it is, would you mind to give the latest
developer snapshot DLL (2014-07-15) from http://cygwin.com/snapshots/ a
try?  Chris has fixed a typo in the above debug message.  If it still
happens for you, maybe the new output helps better to find the cause.


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--GLp9dJVi+aaipsRk
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTxPk9AAoJEPU2Bp2uRE+g6poP/jorRZRhaAvvT3p6E3qkOdCa
CFXKh8HJoSgTGLlWHh0Clbxzrii/LS6uW5pBszsjRfOZEsJvB81nId7+plqklpjz
hD3YLZe1nNzRZBJnRtqP5zZdVKJIkc1rxnEP6qGR4lfp4F9EqHV3S6iKufdYzY/Z
hGXoLVXLQ6abEWviiUYABcCZ3f+ZjlN/xqy+OUkWT6cz1AywXzaAJ15HGgTJwhYZ
ektrcUZ3WFQ5COzFvpt8eml8vGdGKVgfaQoMTgoKRKWRWr4GVpJBNvoWUMIdxSDh
u5sqaLxs7NTiyWHvtBAXhqzJd9xT4LHpRoKLbKQZOyH/2g+eq8knHj95BBKJ6KZ8
Vs8Gji1T4qhNyyvvq0crggFXNMl3PwfhshoiUnoWAPcPOEgPwZSZC4O0Y/uZuNy7
lfY+3aq4KWYMavrLO2BEURsrmu+TBw6WZa468ro4b0EZaCbBz4tV5Gv8fsl1FjOr
di9aX8qiicjTLQSijw0/vwfv2suY8D7xDFfeZeVEIDp1T2FBshx/fQB8GysTJ6Lc
VGj2Zup0oFGCICo7xhngUwYxmaWxPa3MRv1uyd4TjIs4w9T4FXqm1wpKo+/d0v7a
vldJvSbK2FZsgya62TMsf8Z6Y08r+0rBtIkJiBDNJ102j0Ij5cYSp/g81+3SaGh1
Ow+G02T0xq8ycMWj56Zz
=Up9r
-----END PGP SIGNATURE-----

--GLp9dJVi+aaipsRk--

- Raw text -