public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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 10:40:00 -0000	[thread overview]
Message-ID: <7910bbfa-5adf-02ec-39a6-a620180c8695@gmail.com> (raw)
In-Reply-To: <c100f9f7-f722-f1a3-b10a-158b24aa92e4@cs.umass.edu>

On 29/08/2017 23:03, Eliot Moss wrote:
> On 8/29/2017 4:57 PM, Keith Christian wrote:
>> More program failures.  Have rebooted and allowed system to preform 
>> rebase:
>>
>>
>> $ man httping
>>        0 [main] man 7688 child_info_fork::abort:
>> C:\cygwin\bin\cygz.dll: Loaded to different address: parent(0x360000)
>> != child(0x3E0000)
>> man: fork failed: Resource temporarily unavailable
>>
>> Why are all of these programs failing in this way?
> 
> Sometimes I have needed to rebase all programs.  To do this,
> do the command: rebase-trigger full
> If you're not able to run bash to run this, you can run dash
> from Windows CMD and give an explicit path, e.g.,
> 
> /cygdrive/c/cygwin/bin/rebase-trigger full
> 
> would do the right thin on my installation.  But even that won't
> help if you're running 32-bit and have installed too many packages.
> There is only so much room in the address space for the various
> possible DLLs that might be loaded.

Keith,
in addition to Elliot's comment, you can use

   rebase -si

output to  provide an overview of how many dll's are present
and in which address they are mapped.

   $ rebase -si |sort -r --key=5 | head

will provide the list of the one absorbing more address space.
Except the octave-tisean patological case, that I recommend to not 
install if you don't really need it, usually LLVM and ICU
several DLL's are the largest:

  $ rebase -si |sort -r --key=5 | head |awk '{print $5,$1}'
0x020b3000 /usr/bin/cygLLVM-4.0.dll
0x01f75000 /usr/bin/cygQt5WebKit-5.dll
0x01def000 /usr/bin/cygLLVM-3.9.dll
0x01af3000 /usr/bin/cygLLVM-3.8.dll
0x0191d000 /usr/bin/cygicudata59.dll
0x0190a000 /usr/bin/cygicudata58.dll
0x01885000 /usr/bin/cygicudata57.dll
0x017ed000 /usr/bin/cygicudata56.dll
0x01239000 /usr/bin/cyggcj-16.dll
0x00f4f000 /usr/bin/cygoctave-4.dll

Regards
Marco


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

  reply	other threads:[~2017-08-30 10:40 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 [this message]
2017-08-30 12:25             ` Eliot Moss
2017-08-30 12:55               ` Marco Atzeri
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=7910bbfa-5adf-02ec-39a6-a620180c8695@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).