From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 100716 invoked by alias); 14 Feb 2018 01:42:28 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 100700 invoked by uid 89); 14 Feb 2018 01:42:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: Yes, score=6.8 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,HTML_MESSAGE,HTML_OBFUSCATE_05_10,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=alerts, UD:www.cygwin.com, wwwcygwincom, www.cygwin.com X-HELO: mail-ua0-f181.google.com Received: from mail-ua0-f181.google.com (HELO mail-ua0-f181.google.com) (209.85.217.181) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 14 Feb 2018 01:42:25 +0000 Received: by mail-ua0-f181.google.com with SMTP id i5so12751426uai.10 for ; Tue, 13 Feb 2018 17:42:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=WftlPIo6JzXQ8Q/orhROjc+DKe3dtd4oECi8TbHh9Cc=; b=bZy+T9gE1Z8VMn2Hs9zhYKsBlPkpAxaxsqm8DjPRVf5jqVAbGPtT/oMS3v0t9FhNCG GLlRfONS/TFGGYBKdyTE+PosMYeD1nl+dT6pqKBu+nFD1fBI8DFI0QJg1rv/slAa4Ye6 tVQPqV+sv0FXcqaIQJw0jVq3AMoJClwraGT7rZLhI0/uXZISJolLQ7/9/6Z37pmWo6K5 jMlgx0jekD0t4LijSkOve97nXAe8hLP8Yci3W4Fs24iWSz5e3/ANGe3VMGd3ouxETNHZ tFK9ds0KGgE155jb9FFtviHYKOA9ysDkE2qWtWC/akiYkjSW+tGnpUsV8/td0WcfimUe W81Q== X-Gm-Message-State: APf1xPB3sEjUGfI6qkku6WoLtDd9B3LKb35/IYZEKIRBBEmFax5nNLbu FQZrwTJC/B1In3fL6BIrpFDnueR3cEfKkPiOf18= X-Google-Smtp-Source: AH8x226FW5uhgRk1yi2AN1RJ3sKq7whFLe8FjP2olQr3D09ojTSfnx5Zkv1TD/WYgutoY+8bBUXHzThM+p29PgrP7Bs= X-Received: by 10.176.16.210 with SMTP id x18mr2927018uab.15.1518572543377; Tue, 13 Feb 2018 17:42:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.31.47.195 with HTTP; Tue, 13 Feb 2018 17:41:43 -0800 (PST) In-Reply-To: References: <8297ddf5-5d06-c2b1-526b-16ca311749aa@ferzkopp.net> <20180212164945.GA2361@jbsupah> From: Bryan Zimmer Date: Wed, 14 Feb 2018 01:42:00 -0000 Message-ID: Subject: Re: cygwin stopped working To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-02/txt/msg00152.txt.bz2 I have been following this thread closely as I have a similar problem. It only differs in that mintty, which I use to start bash, fails completely. It tells me that it cannot fork, that the problem could be that I have more than 1 cygwin1.dll, that I should run rebaseall or rebase --help. Unfortunately all cygwin processes have the same problem. Even a fresh, clean re-installation of all of cygwin left me with the same problem. On Mon, Feb 12, 2018 at 10:58 PM, Andreas Schiffler wrote: > Found the workaround (read: not really a solution as it leaves the system > vulnerable, but it unblocks cygwin) > - Go to Windows Defender Security Center - Exploit protection settings > - Disable System Settings - Force randomization for images (Mandatory > ASLR) and Randomize memory allocations (Bottom-up ASLR) from "On by > default" to "Off by default" > > Now setup.exe works and can rebase everything; after that Cygwin Terminal > starts as a working shell without problems. > > @cygwin dev's - It seems one of the windows updates (system is on 1709 > build 16299.214) might have changed my ASLR settings to "system wide > mandatory" (i.e. see https://blogs.technet.microsof > t.com/srd/2017/11/21/clarifying-the-behavior-of-mandatory-aslr/ for info) > so that the cygwin DLLs don't work correctly anymore (i.e. see old thread > about this topic here https://www.cygwin.com/ml/cygw > in/2013-06/msg00092.html). This change might have made it into the system > as part of the security update for Meltdown+Spectre (I am speculating), but > that could explain why my cygwin installation that worked fine before (i.e. > mid-2017) stopped working suddenly (beginning 2018). It would be good to > device a test for the setup.exe that checks the registry (likely > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session > Manager\kernel]) for this state and alerts the user. > @jostein - rebase as part of setup.exe had failed as well (see above). > @Achim - that didn't work or do anything (see above). > > > On 2/12/2018 8:49 AM, Jostein Berntsen wrote: > >> On 11.02.18,17:16, Andreas Schiffler wrote: >> >>> Thanks for the tip, but that didn't seem to have helped. >>> >>> The registry setting CYGWIN_NOWINPATH=1 did not seem to affect the >>> environment as seen in bash. >>> >>> The variable seems to be set: >>> >>> bash-4.4$ set >>> ...snip... >>> COMSPEC='C:\WINDOWS\system32\cmd.exe' >>> CYGWIN_NOWINPATH=1 >>> ...snip >>> >>> but the path variable contains still all the common system locations: >>> >>> bash-4.4$ echo $PATH >>> /cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Program Files >>> (x86)/iis express/PHP/v5.3:/cygdrive/c/Program Files/Common Files/Mic >>> rosoft Shared/Windows Live:/cygdrive/c/Program Files (x86)/Common >>> Files/Microsoft Shared/Windows Live:/cygdrive/c/Program Files >>> (x86)/Intel/ >>> iCLS Client:/cygdrive/c/Program Files/Intel/iCLS >>> Client:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:...snip... >>> >>> Manually overriding the PATH variable in bash did not help (presumably >>> because the offending DLL is already loaded): >>> >>> bash-4.4$ export PATH=/usr/local/bin:/usr/bin:/bin >>> bash-4.4$ echo $PATH >>> /usr/local/bin:/usr/bin:/bin >>> bash-4.4$ >>> bash-4.4$ >>> bash-4.4$ ls >>> 0 [main] bash (11276) C:\Cygwin\bin\bash.exe: *** fatal error - >>> cygheap base mismatch detected - 0x3C52410/0x36F2410. >>> 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 >>> installed the cygwin distribution. Rebooting is also suggested if you >>> are unable to find another cygwin DLL. >>> >>> >>> On 2/11/2018 2:42 AM, Doug Henderson wrote: >>> >>>> On 11 February 2018 at 01:18, Andreas Schiffler wrote: >>>> >>>>> Terminal (bash) fails with: >>>>> >>>>> Error: Could not fork child process: Resource temporarily unavailable >>>>> (-1). >>>>> DLL rebasing may be required; see 'rebaseall / rebase --help'. >>>>> >>>>> {snip} >>>> >>>>> 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. >>>>> >>>> {snip} >>>> >>>>> I do have another version of the cygwin dll file on the system (Plex >>>>> installation) but that never caused any issues in the past. >>>>> >>>> {snip} >>>> >>>> Run setup.exe for Cugwin once again and let it rebase. Then reboot and >> see if that works. >> >> Jostein >> >> >> >> -- >> 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 >> >> >> > > -- > 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 > > -- 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