public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: pipe handling errors
Date: Tue, 15 Jul 2014 15:45:00 -0000	[thread overview]
Message-ID: <20140715154534.GQ10401@calimero.vinschen.de> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A702E7EA7FE@USA7109MB022.na.xerox.net>

[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]

Hi Kenneth,

On Jul 15 13:50, Nellis, Kenneth wrote:
> 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>

Thanks.  I just created another snapshot which is supposed to fix this
issue (curtesy cgf).  Can you give it a try, please?


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 --]

  reply	other threads:[~2014-07-15 15:45 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
2014-07-15 13:51   ` Nellis, Kenneth
2014-07-15 15:45     ` Corinna Vinschen [this message]
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=20140715154534.GQ10401@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).