From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages
Date: Wed, 05 Feb 2020 22:07:00 -0000 [thread overview]
Message-ID: <fd409b25-146a-3fcf-ba5d-b7436b4a3f3e@cornell.edu> (raw)
In-Reply-To: <9ed4b0776323e4a0f62191121715d52a0429bdb2.camel@dontech.dk>
On 2/5/2020 4:45 PM, Peter Dons Tychsen wrote:
> Hi David & Co,
>
>> I have started down the road of building cygwin, but did run into a
>> few issues so don't have a debuggable version yet. If you beat me to
>> it, please let me know. Thanks!
>
> Any findings?
>
> I have found something interesting:
>
> 1) If i run the terminal without mintty, the problem goes away. I can
> run my makefiles with "make -j20" without any issues if i start with
> "bash --login" instead of the mintty shortcut, where it just uses the
> normal windows terminal.
>
> 2) As soon as i run via mintty, even "make -j2" quickly goes south,
> causes various fork() issues as we have seen. I will see if i can
> create a small makefile that shows this.
>
> So either the change we are looking for affects mintty, or the actual
> bug we are looking for is in mintty and not the DLL (or both).
>
> Can anyone shed light on this? Another problem is that if i rewind the
> DLL (building previous commits) too much then mintty stops working...
That last issue is probably due to changes in /usr/bin/cygwin-console-helper.exe
related to the new PTY code. So in addition to rewinding the DLL, you have to
rewind cygwin-console-helper.
Ken
--
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:[~2020-02-05 22:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6d43c714-c4ba-4f0c-9913-cb8453129c85@gmail.com>
[not found] ` <d24aa066-ab3d-9ff0-215a-0a1ed1ec2e5d@cornell.edu>
2020-01-01 22:32 ` David Finnie
2020-01-01 23:43 ` David Finnie
2020-01-02 3:02 ` Ken Brown
2020-01-02 21:58 ` Peter Dons Tychsen
2020-01-02 22:29 ` David Finnie
2020-01-02 22:40 ` Ken Brown
2020-02-05 21:46 ` Peter Dons Tychsen
2020-02-05 22:07 ` Ken Brown [this message]
2020-02-06 0:07 ` Takashi Yano
2020-02-05 22:18 ` David Finnie
2020-02-05 22:31 ` Ken Brown
2020-02-05 23:07 ` David Finnie
2020-02-05 23:35 ` Ken Brown
2020-02-07 18:13 ` Brian Inglis
2020-02-07 21:44 ` David Finnie
2020-02-10 20:58 ` Peter Dons Tychsen
2020-02-10 21:34 ` David Finnie
2020-02-11 2:21 ` Takashi Yano
2020-02-11 10:38 ` Peter Dons Tychsen
2020-02-11 10:40 ` Peter Dons Tychsen
2020-02-11 13:16 ` Takashi Yano
2020-02-11 14:21 ` Ken Brown
2020-02-12 14:40 ` Takashi Yano
2020-02-11 21:31 ` Peter Dons Tychsen
2020-02-12 2:25 ` Takashi Yano
2020-02-12 7:50 ` Corinna Vinschen
[not found] ` <20200212112411.32f05ee5ce2c1401bd076746@nifty.ne.jp>
[not found] ` <3971cde6277a16cb04ac25067b4478b9cfbfa319.camel@dontech.dk>
2020-02-13 4:14 ` Takashi Yano
2020-02-13 21:42 ` Peter Dons Tychsen
2020-02-14 1:25 ` Takashi Yano
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=fd409b25-146a-3fcf-ba5d-b7436b4a3f3e@cornell.edu \
--to=kbrown@cornell.edu \
--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).