From: Andreas Schiffler <aschiffler@ferzkopp.net>
To: cygwin@cygwin.com
Subject: cygwin stopped working
Date: Sun, 11 Feb 2018 08:18:00 -0000 [thread overview]
Message-ID: <8297ddf5-5d06-c2b1-526b-16ca311749aa@ferzkopp.net> (raw)
Terminal (bash) fails with:
Error: Could not fork child process: Resource temporarily unavailable (-1).
DLL rebasing may be required; see 'rebaseall / rebase --help'.
PC was rebooted and the cygwin was "refreshed".
Installer (version 2.884, 32bit) fails with:
Package: 0/Perpetual
   0p_000_autorebase.dash exit code 127
   0p_update-info-dir.dash exit code 127
Package: _/base-cygwin
   000-cygwin-post-install.sh exit code 254
Package: _/coreutils
   coreutils.sh exit code 254
Package: _/bash
   bash.sh exit code 254
Package: _/base-files
   base-files-mketc.sh exit code 254
   base-files-profile.sh exit code 254
Package: _/ca-certificates
   ca-certificates.sh exit code 254
Package: _/man-db
   man-db.sh exit code 254
Package: _/mintty
   mintty.sh exit code 254
The shell C:\Cygwin\bin\bash.exe can be launched, but any command fails
to execute with:
bash-4.4$ ls
     1 [main] bash (6316) C:\Cygwin\bin\bash.exe: *** fatal error -
cygheap base mismatch detected - 0x3922410/0x3962410.
This problem is probably due to using incompatible versions of the
cygwin DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version. The most recent version
*should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
I do have another version of the cygwin dll file on the system (Plex
installation) but that never caused any issues in the past.
Thanks for any tips?
--Andreas
--
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 reply other threads:[~2018-02-11 8:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 8:18 Andreas Schiffler [this message]
2018-02-11 10:42 ` Doug Henderson
2018-02-12 1:16 ` Andreas Schiffler
2018-02-12 2:30 ` Brian Inglis
2018-02-12 16:48 ` Jostein Berntsen
2018-02-13 4:58 ` Andreas Schiffler
2018-02-14 1:42 ` Bryan Zimmer
2018-02-14 7:53 ` Eliot Moss
2018-02-14 8:49 ` Marco Atzeri
2018-02-14 3:25 ` W10 Mandatory ASLR default (was: cygwin stopped working) Brian Inglis
2018-02-14 7:17 ` W10 Mandatory ASLR default Thomas Wolff
2018-02-14 7:36 ` Andreas Schiffler
2018-02-16 6:41 ` Brian Inglis
2018-02-18 19:43 ` Andreas Schiffler
2018-02-18 20:07 ` Achim Gratz
2018-02-18 22:40 ` Brian Inglis
2018-02-12 18:16 ` cygwin stopped working 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=8297ddf5-5d06-c2b1-526b-16ca311749aa@ferzkopp.net \
--to=aschiffler@ferzkopp.net \
--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).