Date: Mon, 9 Jan 2023 14:36:44 +0100
To: Brian.Inglis@shaw.ca
Subject: Re: Cygwin 3.4.3 and 3.5.0... hangs in make, top, procps, ls
 /proc/PID/...
Message-ID: <Y7wYbCL7NoeLeXgp@calimero.vinschen.de>
Mail-Followup-To: Brian.Inglis@shaw.ca, cygwin@cygwin.com
References: <4a4427cc-422b-1d14-015e-26523e620d9b@Shaw.ca>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <4a4427cc-422b-1d14-015e-26523e620d9b@Shaw.ca>
UI-OutboundReport: notjunk:1;M01:P0:F/DGrblEVE8=;ThvjDzsnlYaF5vHZcsJ5DH7fLxN
 HmlWDUOcAG9p+vXcDx7dXU0A2EjUaIcK2JaMkeehoSsrtyovoyQsrthXBaXHJSFHotKmI1FWP
 kbgT9VF9imbqsW9prwNd+PN3X+VU1vG1/lSqV4oRgn6yA9TDU705rGe3TIehFnfNWyHGfYZvK
 0OvOFMyxHzhk/8e1Hc3vDI3/408IRDpB6uHjzV07QepQBxoLmkc+sKd2k43s8dCE2YMk/o2YV
 A+ySW2TdBqc/sOkVAL1y8ZMcS82VMVMAjGYLusPOy/7j5hCdVcVFPIfzJm8Z6cT3Q33xS+lSa
 c6qQdLO2I4BIHA6ZWNlzHyxhsil3aYpg36Kk2EX3w8VlyZHgT4EFFiat81qDNadZ25Uy9lUXK
 Bacl6djXvyd1FFj/+haQCaORpeRvIqC2UfOTzOaTSzJHeU/27W3+gisztD1D2TxsHp7N4e4tr
 sYdTzLiGL5FmsqvFFs3FVdFaM3ekEmtkwOCr0ajFIX/l7k1zZKmraFafK9PBaveV2GvPCtoZ2
 lxLbTmvbOmqZiiNmIKLZIOcLDWpT+7eKJslfPoAMhIOL9muQhQ1r2k0giOyCLxXhTHj3sUFtL
 F3/KZ2lVigb/7qJoOvJXwMMjDuwDJzt+WHR2cv3M2a9ZKlCBmumT6jQEBcYRvBmZZZZWjEkyz
 L3qzEeyBJPS74v3TupiplJy+Vc8gr5yCpuN9+/Cq0g==
Precedence: list
From: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>, cygwin@cygwin.com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

Hi Brian,

On Dec 29 21:59, Brian Inglis via Cygwin wrote:
> Hi folks,
> 
> 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?


Thanks,
Corinna

-- 
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