From: Marco Atzeri <marco.atzeri@gmail.com>
To: 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: Wed, 23 Sep 2015 15:56:00 -0000 [thread overview]
Message-ID: <5602CB96.4050808@gmail.com> (raw)
In-Reply-To: <5602BF53.5010203@null.net>
On 23/09/2015 17:03, litter@null.net wrote:
>> It seems a race problem, due to the repetitive fork of grep
>> for every line of some-file
>
> So why does it fail? Seems like a bug to me!
>
> Regards,
> Paul
As does not fail on my computer, I suspect is a race between your AV and
cygwin and sometimes cygwin wins.
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-09-23 15:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2015-09-24 9:51 ` litter
2015-09-24 10:10 ` Marco Atzeri
2015-09-30 11:16 ` litter
2015-10-01 7:03 Vermessung AVT - Wolfgang Rieger
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=5602CB96.4050808@gmail.com \
--to=marco.atzeri@gmail.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).