From: Michael Enright <mike@kmcardiff.com>
To: cygwin@cygwin.com
Subject: Re: Apache rebase trouble
Date: Wed, 24 May 2017 02:53:00 -0000 [thread overview]
Message-ID: <CAOC2fq-9TSLxCH5e+qG4VZHhf56et3t-Oc5WKW+u0UcsrRaxMg@mail.gmail.com> (raw)
In-Reply-To: <op.y0prhbrfaqc5s6@orion.localdomain>
On Tue, May 23, 2017 at 3:59 PM, Michael Lemke wrote:
>
> Lacking further clues I did the trial and error thing and removed some
> stuff I thought I didn't need (like GNOME). Not sure yet what I broke but
> my Apache is working again. Thanks for the hint that the number of known
> dlls could be a problem. I'd still appreciate more precise information
> of how rebase works and if there is a more systematic approach.
>
The command rebase -is gives a list of the DLLs, their sizes and where
they are based.
The DLL size is in "field 5" as 'sort' recons fields, so
rebase -is | sort -k5 will dump the DLLs in size order.
On my system the last DLL in the output is an LLVM DLL which I believe
is used by the X server. A lot of the top DLLs appear to be related to
the X server, some of those are code-generation DLLs for the LLVM JIT
to use. The footprint of the X server seems large.
I haven't updated Cygwin in some time so your results may differ.
--
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-05-23 23:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 0:29 Michael Lemke
2017-05-23 19:51 ` Achim Gratz
2017-05-23 20:05 ` Michael Lemke
2017-05-23 20:17 ` Achim Gratz
2017-05-23 21:02 ` Michael Lemke
2017-05-23 23:56 ` Michael Lemke
2017-05-24 2:53 ` Michael Enright [this message]
2017-05-25 15:29 ` Michael Lemke
2017-05-24 10:14 ` Andrey Repin
-- strict thread matches above, loose matches on Subject: below --
2017-05-21 20:22 Michael Lemke
2017-05-21 20:45 ` Marco Atzeri
2017-05-23 15:25 ` Houder
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=CAOC2fq-9TSLxCH5e+qG4VZHhf56et3t-Oc5WKW+u0UcsrRaxMg@mail.gmail.com \
--to=mike@kmcardiff.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).