From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Presence of cygwin64 elements in an existing Cygwin 32 install after updating
Date: Wed, 30 Aug 2017 12:55:00 -0000 [thread overview]
Message-ID: <e7b0c010-9b88-e0e7-c537-c08920d021be@gmail.com> (raw)
In-Reply-To: <36c2aa01-c5ca-3f6b-e81d-76ec3a2bb2f0@cs.umass.edu>
On 30/08/2017 14:24, Eliot Moss wrote:
> A query related to this:
>
> If I use rebase -si and look at the range of addresses used, what is
> the limit that gets exceeded when I have too many DLLs? In other words,
> what should I look for to determine that I *must* have fewer DLLs?
>
> Regards - Eliot (who uses one ell :-) )
Ehm, sorry Eliot,
you should look if
- you have collisions ( they are signed by * in rebase -si output)
- if you have very low address as allocation is starting at 0x6fff....
and going down.
In my case, where I have already a large number of package,
but not extreme:
$ cygcheck -cd |wc -l
1639
the lowest address is around 0x36960000
32 $ rebase -si |sort --key=3 | head| awk '{print $3, $5,$1}'
0x36960000 0x0000b000 /usr/libexec/coreutils/libstdbuf.so
0x36970000 0x00053000 /usr/lib/xorg/modules/extensions/cygglx.dll
0x369d0000 0x0000d000 /usr/lib/xorg/modules/drivers/nested_drv.dll
0x369e0000 0x0000c000 /usr/lib/xorg/modules/drivers/dummy_drv.dll
0x369f0000 0x00031000 /usr/lib/xorg/modules/cygwfb.dll
0x36a30000 0x0000b000 /usr/lib/xorg/modules/cygshadowfb.dll
0x36a40000 0x00011000 /usr/lib/xorg/modules/cygshadow.dll
0x36a60000 0x0000b000 /usr/lib/xorg/modules/cygfbdevhw.dll
0x36a70000 0x00028000 /usr/lib/xorg/modules/cygfb.dll
0x36aa0000 0x0001e000 /usr/lib/xorg/modules/cygexa.dll
marco@GE-MATZERI-EU ~/doc
32 $ rebase -si |sort --key=3 | tail | awk '{print $3, $5,$1}'
0x6fc90000 0x00088000 /usr/bin/cygGL-1.dll
0x6fd20000 0x0008a000 /usr/bin/cygFLAC-8.dll
0x6fdb0000 0x00019000 /usr/bin/cygFLAC++-6.dll
0x6fdd0000 0x00034000 /usr/bin/cygEMF-1.dll
0x6fe10000 0x0002a000 /usr/bin/cygEGL-1.dll
0x6fe40000 0x0001a000 /usr/bin/cyg4ti2util-0.dll
0x6fe60000 0x00078000 /usr/bin/cyg4ti2int64-0.dll
0x6fee0000 0x00074000 /usr/bin/cyg4ti2int32-0.dll
0x6ff60000 0x00081000 /usr/bin/cyg4ti2gmp-0.dll
0x6fff0000 0x0000b000 /usr/bin/cyg4ti2common-0.dll
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-08-30 12:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 13:36 Keith Christian
2017-08-24 14:21 ` Ken Brown
2017-08-24 16:02 ` Keith Christian
2017-08-29 17:08 ` Keith Christian
2017-08-29 20:57 ` Keith Christian
2017-08-29 21:03 ` Eliot Moss
2017-08-30 10:40 ` Marco Atzeri
2017-08-30 12:25 ` Eliot Moss
2017-08-30 12:55 ` Marco Atzeri [this message]
2017-08-30 14:19 ` Eliot Moss
2017-08-30 13:09 ` Keith Christian
2017-08-30 15:01 ` Marco Atzeri
2017-08-30 17:56 ` Keith Christian
2017-08-30 18:02 ` Keith Christian
2017-08-30 19:11 ` Achim Gratz
2017-08-30 19:49 ` Keith Christian
2017-08-30 20:04 ` Achim Gratz
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=e7b0c010-9b88-e0e7-c537-c08920d021be@gmail.com \
--to=marco.atzeri@gmail.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).