public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: Cygwin <cygwin@cygwin.com>
Subject: Cygwin 3.4.3-1 update cygheap read copy failed Win32 error 299
Date: Sat, 17 Dec 2022 16:15:21 -0700	[thread overview]
Message-ID: <1819e9ed-28c8-52cb-a07e-5e76c0215db9@Shaw.ca> (raw)

Just upgraded all packages including Cygwin last night and get occasional:

0 [main] cygcheck (16308) child_copy: cygheap read copy failed, 
0x0..0x800022F90, done 0, windows pid 16308, Win32 error 299

1 [main] grep (5852) child_copy: cygheap read copy failed, 0x0..0x800717038, 
done 0, windows pid 5852, Win32 error 299

$ uname -srvmo
CYGWIN_NT-10.0-19044 3.4.3-1.x86_64 2022-12-16 12:38 UTC x86_64 Cygwin
$ head /proc/version
CYGWIN_NT-10.0-19044 version 3.4.3-1.x86_64 (runneradmin@fv-az479-541) (gcc 
version 11.3.0 (GCC) ) 2022-12-16 12:38 UTC
$ grep 'cygwin-3\.4\.3' less /var/log/setup.log.full
/var/log/setup.log.full:libsolv:   upgrade   cygwin-3.4.3-1.any
/var/log/setup.log.full:libsolv:   - cygwin-3.3.6-1.any -> cygwin-3.4.3-1.any
/var/log/setup.log.full:libsolv:   upgrade   cygwin-3.4.3-1.any
/var/log/setup.log.full:libsolv:   - cygwin-3.3.6-1.any -> cygwin-3.4.3-1.any
/var/log/setup.log.full:get_url_to_file 
https://muug.ca/mirror/cygwin/x86_64/release/cygwin/cygwin-3.4.3-1.tar.xz 
D:/var/cache/setup/packages/https%3a%2f%2fmuug.ca%2fmirror%2fcygwin%2f/x86_64/release/cygwin/cygwin-3.4.3-1.tar.xz.tmp
/var/log/setup.log.full:Checking SHA512 for 
file://D:/var/cache/setup/packages/https%3a%2f%2fmuug.ca%2fmirror%2fcygwin%2f/x86_64/release/cygwin/cygwin-3.4.3-1.tar.xz
/var/log/setup.log.full:SHA512 verified OK: 
file://D:/var/cache/setup/packages/https%3a%2f%2fmuug.ca%2fmirror%2fcygwin%2f/x86_64/release/cygwin/cygwin-3.4.3-1.tar.xz 
5314acbcb26694afd6aa0a19866ad3ff7472521e184d592c261a145b0c66ce218ca86353614ba42ee3f0fd9f085c206de6f65740a4d83cc93b0547d6ce989f0d
/var/log/setup.log.full:2022/12/16 23:04:45 Downloaded 
D:/var/cache/setup/packages/https%3a%2f%2fmuug.ca%2fmirror%2fcygwin%2f/x86_64/release/cygwin/cygwin-3.4.3-1.tar.xz
/var/log/setup.log.full:2022/12/16 23:05:20 Extracting from 
file://D:/var/cache/setup/packages/https%3a%2f%2fmuug.ca%2fmirror%2fcygwin%2f/x86_64/release/cygwin/cygwin-3.4.3-1.tar.xz
/var/log/setup.log.full:Installing file cygfile:///usr/src/debug/cygwin-3.4.3-1/
...

Downgraded to my own recent test version with cpuinfo changes and no issues.

$ uname -srvmo
CYGWIN_NT-10.0-19044 3.4.0-344.x86_64 2022-12-16 06:55 UTC x86_64 Cygwin
$ head /proc/version
CYGWIN_NT-10.0-19044 version 3.4.0-344.x86_64 (BWI@BWI) (gcc version 11.3.0 
(GCC) ) 2022-12-16 06:55 UTC

Noticed current release is much smaller than previous and my local DLL:

$ TZ=UTC ls -glort /bin/cygwin1*.dll
-rwxr-xr-x 1 3588124 Sep  5 11:17 /bin/cygwin1-prev.dll
-rwxr-xr-x 1 3561202 Dec 16 07:33 /bin/cygwin1-test.dll
-rwxr-xr-x 1 3561202 Dec 16 07:33 /bin/cygwin1.dll
-rwxr-xr-x 1 2951221 Dec 16 12:50 /bin/cygwin1-save.dll
-rwxr-xr-x 1 2951221 Dec 16 12:50 /bin/cygwin1-curr.dll
$ for tar in ~/mirror/x86_64/release/cygwin/cygwin-3.4.?-1.tar.xz; do echo -n 
"${tar##*/}: "; tar -tvf $tar usr/bin/cygwin1.dll | cut -d' ' -f3- ; done
cygwin-3.4.0-1.tar.xz: 3563651 2022-12-04 06:09 usr/bin/cygwin1.dll
cygwin-3.4.1-1.tar.xz: 3563526 2022-12-10 13:12 usr/bin/cygwin1.dll
cygwin-3.4.2-1.tar.xz: 3564074 2022-12-11 05:06 usr/bin/cygwin1.dll
cygwin-3.4.3-1.tar.xz: 2951221 2022-12-16 05:50 usr/bin/cygwin1.dll

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

             reply	other threads:[~2022-12-17 23:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17 23:15 Brian Inglis [this message]
2023-01-02 16:46 ` Size reduction of Cygwin DLL (was Re: Cygwin 3.4.3-1 update cygheap read copy failed Win32 error 299) Jon Turney

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=1819e9ed-28c8-52cb-a07e-5e76c0215db9@Shaw.ca \
    --to=brian.inglis@shaw.ca \
    --cc=Brian.Inglis@SystematicSW.ab.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).