From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: pipe handling errors
Date: Tue, 15 Jul 2014 09:49:00 -0000 [thread overview]
Message-ID: <20140715094949.GJ10401@calimero.vinschen.de> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A702E7EA6EB@USA7109MB022.na.xerox.net>
[-- Attachment #1: Type: text/plain, Size: 2557 bytes --]
On Jul 14 17:40, Nellis, Kenneth wrote:
> 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>
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
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-15 9:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 17:40 Nellis, Kenneth
2014-07-15 9:49 ` Corinna Vinschen [this message]
2014-07-15 13:51 ` Nellis, Kenneth
2014-07-15 15:45 ` Corinna Vinschen
2014-07-15 18:53 ` Nellis, Kenneth
2014-07-15 19:17 ` Nellis, Kenneth
2014-07-15 19:36 ` Nellis, Kenneth
2014-07-15 19:52 ` Christopher Faylor
2014-07-15 20:40 ` Nellis, Kenneth
2014-07-15 22:05 ` Christopher Faylor
2014-07-15 22:27 ` Christopher Faylor
2014-07-16 12:44 ` Nellis, Kenneth
2014-07-16 14:28 ` Christopher Faylor
2014-07-16 17:36 Ti Strga
2014-07-17 8:25 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140715094949.GJ10401@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).