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=hzK
	n4IQNMZ9DVsT8ttNBkPtC3OnfUZyijrLF8rLU9/j2ZH+luQmtLWvET1wd5yS0pW8
	nRlzIvhZ34Wwp8EwFgiHa4Pr86tyN0jXPLXi4K6IwH/PfS263Y1ugf0O7RVLcHFl
	qLtZZ2yFKx9mnVWvKisjNmenrOk7CQaUYj3RCNeo=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: Vermessung AVT - Wolfgang Rieger <w DOT rieger AT avt DOT at>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: Cygwin bash for loops : repeated errors : [main] bash 1972 fork: child -1 - CreateProcessW failed for <bash.exe> errno 9 bash: fork: Bad file descriptor
Date: Thu, 1 Oct 2015 07:03:22 +0000
Message-ID: <AB495CE313664A489959F8DEF45069A90188AA13A3@EXSRV01.avt-imst.local>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

Hi Paul,

I also get Bad File Descriptor errors, though in a quite different situation, see my recent topic "gawk: Bad File Descriptor error with concurrent readonly access to a network file" on Sep 25. There seems to be some issue in some file opening process that occurs with parallel processes and eventually concurrent file access (as in my case). May be the basic problem behind is similar to yours?

Kind regards,
Wolfgang


> After observing for a week on the system with the fix applied, I did not see this issue reoccur.
> I do however still suspect that it is a bug in cygwin, indeed a race condition of some sorts, which probably becomes
> apparent when starting up a process takes (much) longer than expected.
> As said, the guard32.dll is probably scanning the new CreateProcess candidate. I suspect that there's an timing
> assumption in the Cygwin fork code. But as I cannot be sure, I leave it at that.
>
> Regards,
> Paul