public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Vermessung AVT - Wolfgang Rieger <w.rieger@avt.at>
To: "cygwin@cygwin.com" <cygwin@cygwin.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, 01 Oct 2015 07:03:00 -0000	[thread overview]
Message-ID: <AB495CE313664A489959F8DEF45069A90188AA13A3@EXSRV01.avt-imst.local> (raw)

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


             reply	other threads:[~2015-10-01  7:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01  7:03 Vermessung AVT - Wolfgang Rieger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-09-23  7:52 litter
2015-09-23  9:15 ` Marco Atzeri
2015-09-23 15:03   ` litter
2015-09-23 15:56     ` Marco Atzeri
2015-09-24  9:51       ` litter
2015-09-24 10:10         ` Marco Atzeri
2015-09-30 11:16           ` litter

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=AB495CE313664A489959F8DEF45069A90188AA13A3@EXSRV01.avt-imst.local \
    --to=w.rieger@avt.at \
    --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).