From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <izbyshev@ispras.ru>
Received: from mail.ispras.ru (mail.ispras.ru [83.149.199.84])
 by sourceware.org (Postfix) with ESMTPS id 669043858C53
 for <cygwin@cygwin.com>; Wed, 13 Apr 2022 17:27:38 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 669043858C53
Authentication-Results: sourceware.org;
 dmarc=pass (p=none dis=none) header.from=ispras.ru
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=ispras.ru
Received: from mail.ispras.ru (unknown [83.149.199.84])
 by mail.ispras.ru (Postfix) with ESMTPSA id 7FF8E4076255;
 Wed, 13 Apr 2022 17:27:35 +0000 (UTC)
MIME-Version: 1.0
Date: Wed, 13 Apr 2022 20:27:35 +0300
From: Alexey Izbyshev <izbyshev@ispras.ru>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com
Subject: Re: Deadlock of the process tree when running make
In-Reply-To: <20220414022206.208a9fbba80e926042d77a7a@nifty.ne.jp>
References: <9388316255ada0e0fcb2d849cce5a894@ispras.ru>
 <20220409191743.6da2268a36e8c9b4ab22c722@nifty.ne.jp>
 <1ecd670b1cdff43e0b0d7e5ee4c9cfc5@ispras.ru>
 <ab3971adb8f441fd16bb62e480547a95@ispras.ru>
 <20220409204619.dd0e53902d5e108ef462e510@nifty.ne.jp>
 <907ce1b4416a826cb07990dd601bd687@ispras.ru>
 <20220410015753.753e2a238513eaf2a3da81e9@nifty.ne.jp>
 <f55466cdda02fa46bc43174ba412df3a@ispras.ru>
 <20220410025410.196aa0a04368147dbbb31d3e@nifty.ne.jp>
 <afad32070411d6d94d5d94da90478af4@ispras.ru>
 <7204ed0aa2d6b3fcfb239010e6b67646@ispras.ru>
 <20220410163432.00dd7b9f81f8f322d97688f2@nifty.ne.jp>
 <0e1a53626639cb21369225ff9092ecfc@ispras.ru>
 <b937a782f8b8993e3d4a058a354596a7@ispras.ru>
 <20220411173526.6243b9492e0fc3d4132a58a8@nifty.ne.jp>
 <ab8ded5fb5dad09dc2aebe5b49aa7dac@ispras.ru>
 <1bdd5ac77277343fbff9b560fa98b15e@ispras.ru>
 <20220414022206.208a9fbba80e926042d77a7a@nifty.ne.jp>
User-Agent: Roundcube Webmail/1.4.4
Message-ID: <297c3c633621e640340922fd661219f1@ispras.ru>
X-Sender: izbyshev@ispras.ru
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_00, DOS_RCVD_IP_TWICE_B,
 KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2022 17:27:39 -0000

On 2022-04-13 20:22, Takashi Yano wrote:
> On Wed, 13 Apr 2022 19:48:04 +0300
> Alexey Izbyshev wrote:
>> On 2022-04-11 13:10, Alexey Izbyshev wrote:
>> The good news is that the tests have been running for two days so far
>> without any cygwin-related issues, so the patched version doesn't seem
>> to introduce new issues.
>> 
> Thanks for testing.
> 
> Question is:
> Is the issue reproduced using new cygwin1.dll? Or is it still
> running without the issue so far?

It's still running without any issues with the new DLL. The experiment 
with closing a handle was done with the old hanging tree.

Alexey