From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.4.5-1
Date: Thu, 19 Jan 2023 17:26:59 -0700 [thread overview]
Message-ID: <8216283e-2158-d136-11bc-ed020f5161ba@Shaw.ca> (raw)
In-Reply-To: <announce.20230119211631.505798-1-corinna-cygwin@cygwin.com>
On 2023-01-19 13:16, Corinna Vinschen via Cygwin wrote:
> The following packages have been uploaded to the Cygwin distribution:
> * cygwin-3.4.5-1
> * cygwin-devel-3.4.5-1
> * cygwin-doc-3.4.5-1
> The 3.4.4 release had to be skipped for technical reasons.
> Bug Fixes
> ---------
> - Fix an uninitialized variable having weird side-effects in path handling.
> Addresses: https://cygwin.com/pipermail/cygwin/2022-December/252734.html
> - Fix hang-up of less on quit which occurs when it is started from non-cygwin
> shell and window is resized.
> Addresses: https://cygwin.com/pipermail/cygwin/2022-December/252737.html
> - Reinstantiate exporting _alloca.
> Addresses: https://cygwin.com/pipermail/cygwin/2023-January/252797.html
> - Avoid hangs when reading /proc/<PID>/status.
> Addresses: https://cygwin.com/pipermail/cygwin/2022-December/252756.html
> - Fix vmstat(1) printing an error message on single core CPUs.
> Addresses: https://cygwin.com/pipermail/cygwin/2023-January/252857.html
> - Fix potential process termination during process initialization.
> Most easily reproducible is the case of non-Cygwin processes running
> with high-entropy VA enabled and loading the Cygwin DLL dynamically.
> Addresses: https://cygwin.com/pipermail/cygwin/2023-January/252765.html
> https://cygwin.com/pipermail/cygwin/2023-January/252865.html
> - Fix a build problem breaking cygcheck and strace.
> Addresses: https://cygwin.com/pipermail/cygwin/2023-January/252894.html
Looking much better - installed and surviving a couple of cygcheck loops still
running, ncurses build completed no issues, curl build and tests ongoing, top
running, cron jobs continuing, X clients running under server - no issues so far.
Will push ncurses build to Scallywag to see if those errors are gone.
--
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
prev parent reply other threads:[~2023-01-20 0:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 20:16 Corinna Vinschen
2023-01-20 0:26 ` Brian Inglis [this message]
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=8216283e-2158-d136-11bc-ed020f5161ba@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).