pipe handling errors

Nellis, Kenneth Kenneth.Nellis@xerox.com
Tue Jul 15 13:51:00 GMT 2014


From: Corinna Vinschen
> 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
> > 
> <snip>
> 
> 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.

FYI, got it again this morning, this time with the suggested snapshot:

      0 [main] -bash 8812 sig_send: error sending signal -66, pid 8812, pipe handle 0x80, nb 0, packsize 176, Win32 error 0

Cygwin64> uname -srvmo
CYGWIN_NT-6.1 1.7.31s(0.273/5/3) 20140715 09:22:44 x86_64 Cygwin
Cygwin64>


More information about the Cygwin mailing list