From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 70145 invoked by alias); 13 Feb 2018 04:58:34 -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 70134 invoked by uid 89); 13 Feb 2018 04:58:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=no version=3.3.2 spammy=alerts, UD:www.cygwin.com, wwwcygwincom, www.cygwin.com X-HELO: mout.perfora.net Received: from mout.perfora.net (HELO mout.perfora.net) (74.208.4.197) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 13 Feb 2018 04:58:32 +0000 Received: from [192.168.1.109] ([24.18.200.169]) by mrelay.perfora.net (mreueus003 [74.208.5.2]) with ESMTPSA (Nemesis) id 0LaUu1-1eOCvy486x-00mJgE for ; Tue, 13 Feb 2018 05:58:30 +0100 Subject: Re: cygwin stopped working To: cygwin@cygwin.com References: <8297ddf5-5d06-c2b1-526b-16ca311749aa@ferzkopp.net> <20180212164945.GA2361@jbsupah> From: Andreas Schiffler Message-ID: Date: Tue, 13 Feb 2018 04:58:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180212164945.GA2361@jbsupah> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-UI-Out-Filterresults: notjunk:1;V01:K0:Xavr7jfQOuo=:+vkncEO4kyTkuo94TwrhVz J3BsPO2aW0yGwOr854kPfjADFfS/GHRhK1IGtr+OoKiWNoXswxnSRu22t625IMiKxvHciEE5E e399z1iMMi5uYAmyOPpG6l6qaDp6u5DCHKwOxHiWGjcYq8Uwi27mNpjWHYUsYsvgPnwM6k71e jw1e3fc+uPTDx0tgldm+Xkh4FN/Mtz4KpAht692jF+HmJUbwVtPAezkLD3KvgWPovh9X0sf0T OYsblvGfYOP721vNgjOr5Htkqe++jYDNfO2L0grzXeUPGwNSKCK940lx6/Ch9C3RcrVK4kYtA Y1mQAS6K5B2udeMcw1b5TlAVOAL9PI554lpYbCsTEV0cyWnhgdcDTBZ65pJ3LjPH6UzDnxlms 4bMgwg7F2J1WpiNK5YjpL4ih4TJVB965grB3r7wWgCs6pzSGLSr0JJMbT9xQZ7IStUffpOpcf ZdFeZpe8POju6/s9Tdt7B5sKfNBRDi5KAwAR2oOX6I51x1rl9Ef8rFWDhQGSrDM5VpFukdu5h e4ajTiukF9itnTtEzKrskHa+V63owTlTBbcz2f+f4Tf7tNIBdthfgL89shGiFujG8/Heq5dYL zBrs7YWZ+Igbxn1aGsD3orh0p+Q5+TKYHeHfiXM/aupPSNxma16bWPNoG+JCINYnmSEh33pOZ 6lNOT7PSCmJL1RSMpfwiLUPyYMLscGXbFyaMSA7UXEME4XIjxLGJ7LHlvR5QNu5TSlGNSRjUH vPLUVgRsKu+aHaw1jeAA640ksdUfdcJUHGlJ19mZLik1de6KxQmeOTc7SH4= X-IsSubscribed: yes X-SW-Source: 2018-02/txt/msg00129.txt.bz2 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.microsoft.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/cygwin/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