From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: fork() fails if it is called recursively from a child thread.
Date: Thu, 09 Mar 2017 16:16:00 -0000 [thread overview]
Message-ID: <20170310011502.9677cedf4038c5f4dc1e89cd@nifty.ne.jp> (raw)
In-Reply-To: <882e88d5-d508-fee8-e22c-47434297e8c8@cs.umass.edu>
On Thu, 9 Mar 2017 08:53:19 -0500 Eliot Moss wrote:
Thank you for response.
> This strikes me as either BLODA (interfering software) or a need to
> rebase some dll(s). That's what I most commonly see that causes that
> fork error.
This occurs even under newly installed windows 10 & 7.
Moreover, rebaseall does not help.
Couldn't you reproduce the problem in your environment with my test case?
Release note of iperf 2.0.5-1 says:
Note that a currently known limitation of the Cygwin version is that
running as a daemon (with the -D option) is not currently functional.
The previous version (2.0.4) also had this limitation.
This is also the reason why I think this problem causes commonly
with cygwin.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
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:[~2017-03-09 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 11:40 Takashi Yano
2017-03-09 13:53 ` Eliot Moss
2017-03-09 16:16 ` Takashi Yano [this message]
2017-03-09 17:06 ` Achim Gratz
2017-03-09 17:33 ` Takashi Yano
2017-03-09 19:48 ` cyg Simple
2017-03-10 20:10 ` Corinna Vinschen
2017-03-11 1:29 ` Takashi Yano
2017-03-21 15:05 ` Erik Bray
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=20170310011502.9677cedf4038c5f4dc1e89cd@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).