This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.7.1-1 Install freeze of Cygwin post

On Sun, Dec 27, 2009 at 10:48:39PM -0500, Brian Wilson wrote:
>I'm running a Dell XPS (single core 3GHz processor) with WinXP SP3 with latest 
>patches.  My system has 4GB memory installed and 20GB free disk space 
>I had 1.5 installed and working well.  I tried to upgrade to 1.7 and received 
>many errors and could not complete the installation because the installation 
>appeared to stop working.  I rebooted several times and retried the update 
>each time with no success.  I manually removed all cygwin files and cleaned 
>the registry.  I tried downloading the setup and reinstalling the base 1.7 
>release.  Everything goes find until I get to the /etc/postinstall/000-cygwin-
> step and the progress bars stop showing any progress (i.e. 
>appear to stop working).
>I went to c:\cygwin\var\log\setup.log.postinstallXa01348 and looked at this 
>file.  It contains:
>  5 [main] bash 508 C:\cygwin\bin\bash.exe: *** fatal error - couldn't 
>allocate heap, Win32 error 487, base 0x6D0000, top 0x730000, reserve_size 
>389120, allocsize 393216, page_const 4096
>      5 [main] bash 2216 child_info::sync: wait failed, pid 508, Win32 error 0
>    909 [main] bash 2216 fork: child -1 - died waiting for longjmp before 
>initialization, retry 0, exit code 0x1000000, errno 11
>I have no choice but to cancel the install and retry; but it never completes 
>and always fails at the same point.  Does anyone know what this means and how 
>to fix the problem?  If it's something stupid I've done; please point out the 

Just as a wild guess, given the minimal information above, and given the
handful of other problems reported with this - you may have two versions
of Cygwin installed on your system.  One would be installed in a
standard location and another could be in windows\system32 or in a
third-party location like cwrsync or in some other cygwin repackager.

See: .  Run the cygcheck command
suggested there and inspect the output for clues.  Also look in your
windows directory and along your PATH for other copies of cygwin1.dll
and any other Cygwin DLLs.


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]