public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: Cygwin64: Rebase problems
Date: Sat, 02 Nov 2013 20:03:00 -0000	[thread overview]
Message-ID: <52755A75.1000700@tiscali.co.uk> (raw)
In-Reply-To: <5274DCA9.7020408@tiscali.co.uk>

On 02/11/2013 11:06, David Stacey wrote:
> I'm trying to reinstall 64-bit Cygwin, using a snapshot taken on 
> 2013-10-24. The post-install step goes into an infinite loop whilst 
> running 'texlive-collection-basic.sh': perl is attempting to load some 
> modules (IO.dll, MD5.dll, Fcnt.dll, Cwd.dll), which fail with rebase 
> errors. The script waits five seconds before trying (and failing) 
> again; this repeats ad infinitum.
>
> Here is an extract from the setup log:
>
>       0 [main] perl 3384 child_info_fork::abort: address space needed 
> by 'IO.dll' (0x300000) is already occupied
> Can't fork, trying again in 5 seconds at /usr/bin/updmap line 54.
>       0 [main] perl 3404 child_info_fork::abort: unable to remap 
> MD5.dll to same address as parent (0x2E0000) - try running rebaseall
> Can't fork, trying again in 5 seconds at /usr/bin/updmap line 54.
>       0 [main] perl 3452 child_info_fork::abort: address space needed 
> by 'IO.dll' (0x300000) is already occupied
> Can't fork, trying again in 5 seconds at /usr/bin/updmap line 54.
>       0 [main] perl 3456 child_info_fork::abort: address space needed 
> by 'IO.dll' (0x300000) is already occupied
> Can't fork, trying again in 5 seconds at /usr/bin/updmap line 54.
>       0 [main] perl 3408 child_info_fork::abort: unable to remap 
> Fcntl.dll to same address as parent (0x2F0000) - try running rebaseall
> Can't fork, trying again in 5 seconds at /usr/bin/updmap line 54.
>
> The error message suggests running rebaseall - however, 
> 'autorebase.bat' was run a few seconds earlier.
>
> I launched bash (from 'cmd') and ran 'rebase -si' and the results are 
> attached. There are two things to note. Firstly, a great many entries 
> have a base address of zero(!). Secondly, the last six entries in the 
> file have a rather large base address - I would expect the addresses 
> to start around 0x400000000 and decrease.
>
> If I delete '/etc/rebase.db.x86_64' and run 'rebaseall -p -v' then 
> everything seems to work OK - running 'rebase -si' gives sensible 
> output, and the 'texlive-collection-basic.sh' post-install script runs.

Neither 'rebase' nor 'dash' have changed since my last successful 
install - but 'setup-x86_64.exe' has changed. Clutching firmly to this 
straw, I tried version 2.819 - and this behaved in exactly the same way 
to version 2.830. Still, when you have eliminated the impossible...

'rebase' depends on 'grep', which /has/ changed recently. However, if 
'grep' was playing up then this list would be awash with complaints from 
confused users. No - it can't be that. My next step is to work 
backwards, starting with my snapshot and plodding backwards in time 
until I find the cause.

Dave.



--
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:[~2013-11-02 20:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-02 11:12 David Stacey
2013-11-02 20:03 ` David Stacey [this message]
2013-11-23 19:35 ` David Stacey
2013-11-25 19:28   ` Larry Hall (Cygwin)
2013-11-30  6:32 ` [PATCH] 'rebase' uninitialised variable (was: Cygwin64: Rebase problems) David Stacey
2013-12-01 12:23   ` Corinna Vinschen
2013-12-03  2:20     ` Jason Tishler
2013-12-03 10:22       ` Corinna Vinschen
2013-12-03 15:43       ` GOLD STAR (was Re: [PATCH] 'rebase' uninitialised variable) Christopher Faylor
2013-12-03 16:05         ` Corinna Vinschen
2013-12-03 16:10           ` Christopher Faylor
2013-12-03 16:32             ` Corinna Vinschen
2013-12-06 15:41         ` Andrew Schulman

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=52755A75.1000700@tiscali.co.uk \
    --to=drstacey@tiscali.co.uk \
    --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).