From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 96988 invoked by alias); 11 Feb 2020 13:16:45 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 96975 invoked by uid 89); 11 Feb 2020 13:16:44 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy= X-HELO: conssluserg-01.nifty.com Received: from conssluserg-01.nifty.com (HELO conssluserg-01.nifty.com) (210.131.2.80) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 11 Feb 2020 13:16:41 +0000 Received: from Express5800-S70 (ntsitm196171.sitm.nt.ngn.ppp.infoweb.ne.jp [125.0.207.171]) (authenticated) by conssluserg-01.nifty.com with ESMTP id 01BDFvDc019303; Tue, 11 Feb 2020 22:15:57 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com 01BDFvDc019303 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp; s=dec2015msa; t=1581426957; bh=fz1FHWoMiuS+OWUK8qKhEVwHqjrHA17AqsZuanjCbiM=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=yUM2zW1EggwiQ7U9vydoBxsBaKBDH800SbswEwFi6w1Q5uOWuYYsHehRjsWu2AlgZ dsmZ65jGQ5HnND0RAlSf17GGKWO4lq6BZJMJ1G6UhGskE9OWJRhkGcr3YjUS0bCmtW bhFVRPqaoxgWP28QQeRVLuJFzisEPXEWxTq3+vdzNCaCky4QwwkfFRNup8MKRgtefi xaN7TcAlepzekyolmQ2Ez4cnGwVaS9RWIJH7TaY+UCUOhZKaS/e2vLxH7Pj9dWW1HY +K7alJvB23o+gaGOkSGGFUWNrz6gRcGgUIUIZyJHciIAqWuMRIrNkS8Nbc8/bjcHa8 lu/2ALd3wImnw== Date: Tue, 11 Feb 2020 13:16:00 -0000 From: Takashi Yano To: cygwin@cygwin.com Cc: pdt@dontech.dk Subject: Re: fork: Resource temporarily unavailable errors after upgrading cygwin packages Message-Id: <20200211221606.c82d718ec32a6d0ce3c2ad7b@nifty.ne.jp> In-Reply-To: References: <6d43c714-c4ba-4f0c-9913-cb8453129c85@gmail.com> <93562f34-3a14-0c10-cb57-1ae861307d82@gmail.com> <810b0c97ee0697c06bdaa4dff4081bb502bc46ab.camel@dontech.dk> <9ed4b0776323e4a0f62191121715d52a0429bdb2.camel@dontech.dk> <23d3cd65794886745e2070a1d1b74013418b0bd8.camel@dontech.dk> <20200211112026.05664f5c68b6282a39da8ac2@nifty.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2020-02/txt/msg00098.txt.bz2 On Tue, 11 Feb 2020 11:38:35 +0100 Peter Dons Tychsen wrote: > On Tue, 2020-02-11 at 11:20 +0900, Takashi Yano wrote: > > Is this the same as your problem? > > Yeah, it could be. Could this result in fork error messages as we are > seeing all over the place? No. Fork error is not seen in my environment. This could be another problem. However, the code using kill() below is called also by fork(). So, it may be related. I have not investigated your problem on make, so the mechanism to cause the problem is not clear. I do not have confidence that this patch really fixes your problem. > > If so, it goes without stopping 1 minute with patch: > > https://cygwin.com/ml/cygwin-patches/2020-q1/msg00148.html > > Nice trick to use pinfo as a work-around, but i could fear that others > also call kill() at this critical time. Is there an actual fix for > kill() in the cooking? I could fear that tools like "make" actually > call this all over the place, especially if its aborting running > processes. And why did this work before? The commit message says: > This seems to be caused by invalid pointer access which occurs > when the process exits during the kill() code is execuetd. This > patch avoids the issue by not using kill(). however, I found the real cause is that errno is accidentally set by kill() in pty system calls. That is, the problem is not in the kill() itself but in usage of it. Cygwin older than 3.1.0 does not have these code in pty. On Tue, 11 Feb 2020 11:40:45 +0100 Peter Dons Tychsen wrote: > And why does it work when running without minnty? How does that play > into this? The code which has this problem is in the pty code. So, this occurs only in pty such as mintty, xterm, etc. Console (cygwin in command prompt) does not use pty, so problem does not occur in console. -- Takashi Yano -- 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