From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis via Cygwin <cygwin@cygwin.com>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Cygwin 3.4.3 and 3.5.0... hangs in make, top, procps, ls /proc/PID/...
Date: Mon, 16 Jan 2023 15:40:32 +0000 [thread overview]
Message-ID: <595ad9b9-9631-2df9-bea8-6bc4516b34d8@dronecode.org.uk> (raw)
In-Reply-To: <1d8041cd-5545-00d2-1cdf-3e7b6d12a824@Shaw.ca>
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)
next prev parent reply other threads:[~2023-01-16 15:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 4:59 Brian Inglis
2023-01-02 2:32 ` Takashi Yano
2023-01-02 5:38 ` Takashi Yano
2023-01-02 8:21 ` Takashi Yano
2023-01-09 13:20 ` Corinna Vinschen
2023-01-16 9:02 ` Takashi Yano
2023-01-16 10:23 ` Corinna Vinschen
2023-01-16 14:45 ` Takashi Yano
2023-01-16 15:18 ` Corinna Vinschen
2023-01-16 19:23 ` Brian Inglis
2023-01-16 21:42 ` Corinna Vinschen
2023-01-17 20:46 ` Corinna Vinschen
2023-01-18 9:16 ` Takashi Yano
2023-01-18 9:42 ` Corinna Vinschen
2023-01-19 16:31 ` Brian Inglis
2023-01-19 17:12 ` Brian Inglis
2023-01-19 18:38 ` Corinna Vinschen
2023-01-19 18:42 ` Jose Isaias Cabrera
2023-01-19 19:31 ` Brian Inglis
2023-03-21 19:17 ` Brian Inglis
2023-03-22 19:05 ` Brian Inglis
2023-01-02 23:03 ` Takashi Yano
2023-01-09 16:02 ` Corinna Vinschen
2023-01-09 17:13 ` Corinna Vinschen
2023-01-10 10:01 ` Takashi Yano
2023-01-10 10:57 ` Corinna Vinschen
2023-01-09 13:36 ` Corinna Vinschen
2023-01-10 0:00 ` Brian Inglis
2023-01-16 15:40 ` Jon Turney [this message]
2023-01-16 18:54 ` Brian Inglis
2022-12-31 20:01 Brian Inglis
2023-01-01 18:51 ` Jeremy Drake
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=595ad9b9-9631-2df9-bea8-6bc4516b34d8@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).