From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin 3.4.3 and 3.5.0... hangs in make, top, procps, ls /proc/PID/...
Date: Thu, 19 Jan 2023 19:38:41 +0100 [thread overview]
Message-ID: <Y8mOMVn1RL8/BnhE@calimero.vinschen.de> (raw)
In-Reply-To: <f49aab6a-2cda-ba21-27d1-c4021a18f292@Shaw.ca>
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.
>
> When cygcheck -hrsv was run as usual in local postinstall script
> zp_z2_l_cygcheck-hrsv.dash gave error msg box can't find zlib1.dll - but
> it's there:
>
> $ ls -glo /usr/x86_64-w64-mingw32/sys-root/mingw/bin/zlib1.dll
> -rwxr-xr-x 1 117267 Oct 15 12:14
> /usr/x86_64-w64-mingw32/sys-root/mingw/bin/zlib1.dll
>
> Under X/mintty/bash cygcheck will not even start - says so in error msg box
> with code 0xc000007b!
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,
Corinna
next prev parent reply other threads:[~2023-01-19 18:38 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 [this message]
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
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=Y8mOMVn1RL8/BnhE@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).