From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin 3.4.3 and 3.5.0... hangs in make, top, procps, ls /proc/PID/...
Date: Wed, 22 Mar 2023 13:05:44 -0600 [thread overview]
Message-ID: <6cd15fcf-8f55-4bba-220d-61f970669251@Shaw.ca> (raw)
In-Reply-To: <f980e410-2abc-83b6-5a8c-c0870e2f082d@Shaw.ca>
On 2023-03-21 13:17, Brian Inglis wrote:
> On 2023-01-19 12:31, Brian Inglis via Cygwin wrote:
>> On 2023-01-19 11:38, Corinna Vinschen via Cygwin wrote:
>>> On Jan 19 09:31, Brian Inglis via Cygwin wrote:
>>>> On 2023-01-18 02:42, Corinna Vinschen via Cygwin wrote:
>>>>> I tested this yesterday with 7 runs on two machines in parallel while
>>>>> building Cygwin continuously in another Window, and cygcheck still with
>>>>> high-entropy-VA enabled. And one of the machines continued to run the
>>>>> cygcheck loops over night and were still in good shape this morning :)
>>>>> I guess we should release 3.4.4 pretty soon now.
>
>>>> I installed and tested 3.5.0-0.122.g3c2ac163da88.x86_64 instead, as that was
>>>> the autoselected test version.
>
>>> Drat. I pushed a patch. This is fixed in 3.5.0-0.124.g1d4110e347ad.x86_64
>>> and the upcoming 3.4.5 (had to skip 3.4.4, don't ask...)
>
>> Thanks, will test when available to upgrade. ;^>
>> Also took precautions in postinstall script PATH just in case.
>
> Just built, tested, and released curl no problem, but coreutils with make
> 4.4.1-1 hung up with procps, top, and bash kill, but not ls /proc/...
>
> $ uname -srvmo
> CYGWIN_NT-10.0-19044 3.5.0-0.231.g93f70d7849b8.x86_64 2023-03-07 03:11 UTC
> x86_64 Cygwin
>
> Attached current cygcheck
>
> Only test packages are cygwin 3.5.0 and gcc 11.3
>
> Will reinstall current stable and retry unless anyone wants me to try something?
Reinstalled current stable cygwin 3.4.6-1 and gcc 11.3.0-1 and still hangs.
/bin/kill mostly works but sometimes also hangs and needs killed from TaskMgr.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-03-22 19:05 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 [this message]
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
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=6cd15fcf-8f55-4bba-220d-61f970669251@Shaw.ca \
--to=brian.inglis@shaw.ca \
--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).