X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5FEB03858422
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1673883673;
	bh=M2mJ2j8ncAu3t+4+o5haFYSOVS4sGuBxpxEcE5C+3ts=;
	h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=yvsATCvGmZ5wXaQbkF1hbNzGcsY61dZXVQ0NyJrIK4dOJgBScySuhrli5IdjkH1H/
	 aqpuAdfo9CcKS3dt2E1EnrCCADgTWEh6bSUNkdKzpRTvCO5nVkU2Hnal+6ceIUK+u/
	 dYMzGZgBYG2r59+pU1wz2eAsWrhGhG68bSa3gf64=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org D71953858D32
X-SNCR-Rigid: 613A901C4B29E3E5
X-Originating-IP: [81.153.98.246]
X-OWM-Source-IP: 81.153.98.246 (GB)
X-OWM-Env-Sender: jonturney AT btinternet DOT com
X-VadeSecure-score: verdict=clean score=0/300, class=clean
X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedvhedruddtgedgkedtucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpeflohhnucfvuhhrnhgvhicuoehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkqeenucggtffrrghtthgvrhhnpedvtdetffekveevjeegheeglefhtdeggfeilefggfdutedufedvgefgieeiffdtveenucfkphepkedurdduheefrdelkedrvdegieenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddruddtiegnpdhinhgvthepkedurdduheefrdelkedrvdegiedpmhgrihhlfhhrohhmpehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkpdhnsggprhgtphhtthhopedupdhrtghpthhtoheptgihghifihhnsegthihgfihinhdrtghomh
X-RazorGate-Vade-Verdict: clean 0
X-RazorGate-Vade-Classification: clean
Message-ID: <595ad9b9-9631-2df9-bea8-6bc4516b34d8@dronecode.org.uk>
Date: Mon, 16 Jan 2023 15:40:32 +0000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.6.1
Subject: Re: Cygwin 3.4.3 and 3.5.0... hangs in make, top, procps, ls
 /proc/PID/...
Content-Language: en-GB
To: Brian Inglis via Cygwin <cygwin AT cygwin DOT com>,
        The Cygwin Mailing List <cygwin AT cygwin DOT com>
References: <Y7wYbCL7NoeLeXgp AT calimero DOT vinschen DOT de>
 <1d8041cd-5545-00d2-1cdf-3e7b6d12a824 AT Shaw DOT ca>
In-Reply-To: <1d8041cd-5545-00d2-1cdf-3e7b6d12a824@Shaw.ca>
X-Spam-Status: No, score=-1191.8 required=5.0 tests=BAYES_00, FORGED_SPF_HELO,
 KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
 SPF_HELO_PASS, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Jon Turney via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 30GFfdco030412

On 10/01/2023 00:00, Brian Inglis via Cygwin wrote:
> On Mon, 9 Jan 2023 14:36:44 +0100, Corinna Vinschen wrote:> On Dec 29 
> 21:59, Brian Inglis via Cygwin wrote:
>>> I got some hangs (deadlock?) between (parallel?) make jobs, top, 
>>> procps, and
>>> even ls /proc/*/ when trying to cygport all check curl or look at the
>>> process statuses when builds hung under Cygwin 3.4.3 and 3.5.0-0.69...
>>> Had to revert to a Cygwin 3.4.0-344 test build from Dec 16 sources to 
>>> build
>>> and check curl etc.
> 
>> Given this looks like a regression, we'd need the exact version of the
>> test DLL you were using.  I. e., what SHA1 id did your HEAD have when
>> you built this test DLL?
> 
> No way for me to tell now.
> Tried more recent pulls and builds since.
> Is there any trace of pulls done?

'git reflog' contains something like that information.

(This doesn't show dates by default, so something like 'git reflog 
--date=iso', might be more helpful in working out what HEAD was at some 
point in the past)


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple