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: Sat, 11 Mar 2017 01:29:00 -0000 [thread overview]
Message-ID: <20170311102929.f4bca99e253d6560566cbfb7@nifty.ne.jp> (raw)
In-Reply-To: <20170310201036.GA18927@calimero.vinschen.de>
Hello,
On Fri, 10 Mar 2017 21:10:36 +0100 Corinna Vinschen wrote:
> Thanks for the report and especially the testcase.
>
> It was a tricky problem to debug so it took me a while, but I think
> I got it now.
>
> I uploaded new developer snapshots to https://cygwin.com/snapshots/
>
> Please give them a try. I'd be also interested if that fixes the iperf
> problem. Can you check? There's always a chance that this uncovers
> another problem hidden under this one...
I tested the new snapshot, and confirmed the issue was fixed.
The test case as well as iperf 2.0.5 with options -s -D works
without problem.
At least in my short test, I couldn't find any other hidden
problems.
Thank you very much!
--
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-11 1:29 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
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 [this message]
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=20170311102929.f4bca99e253d6560566cbfb7@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).