From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Size reduction of Cygwin DLL (was Re: Cygwin 3.4.3-1 update cygheap read copy failed Win32 error 299)
Date: Mon, 2 Jan 2023 16:46:14 +0000 [thread overview]
Message-ID: <e8d281f5-3ac0-bd27-fb11-e384b7572c3b@dronecode.org.uk> (raw)
In-Reply-To: <1819e9ed-28c8-52cb-a07e-5e76c0215db9@Shaw.ca>
On 17/12/2022 23:15, Brian Inglis via Cygwin wrote:
> Just upgraded all packages including Cygwin last night and get occasional:
[...]
>
> 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
This is probably not related to any problems you are seeing.
In 3.4.3 we made a change so that cygwin DLL is stripped by the standard
mechanisms in cygport (previously it managed it's own stripping) [1].
It seems that cygport does a more thorough job of this (in particular it
removes the (I think useless) COFF symbol table).
[1]
https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=99bb3e937a0fdbc1e3acbdc7cefb31e54a89a6ac
prev parent reply other threads:[~2023-01-02 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 23:15 Cygwin 3.4.3-1 update cygheap read copy failed Win32 error 299 Brian Inglis
2023-01-02 16:46 ` Jon Turney [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=e8d281f5-3ac0-bd27-fb11-e384b7572c3b@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).