X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Y6JLMG3RIpfOljn3
	QzAX69GR2VzTvkEYcbJaLC+heKdsCN7GkQ/e4beWQVD6PVMUDy2TpcG12cDNtjZ3
	qp7RVQn0wqxN+DQAtfV70MJqkIhtGtmXBuH/w8Rjs9JMDO/XeCD9RaZdE8TRjysH
	FIq5pBJbDw2miPLl5cpUeM3OXUE=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=+9MEydfwTq1MiBj65wnTQy
	JPyw8=; b=pn7r2OvTqkFoAte5x5REHNOlA2Phl8vjTQlV/nUl49RkJawmJaYcx+
	cYuMT4WzJOvHoPliGabf3jkxIDpEAofypxRf49pcri7MIFANSCXW8ovlLfdtuQBK
	mKRKlfbYkoAi0DCRwhMWSzCv7MuUaIm1WOCBCyFKl8junl5r0wW4s=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
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
Subject:	Re: cygwin stopped working
To:	cygwin AT cygwin DOT com
References:	<8297ddf5-5d06-c2b1-526b-16ca311749aa AT ferzkopp DOT net> <CAJ1FpuMivfg+RKg3kDf8rt6n-Ky0Ami_5_HpGjbAMGpHgM57Tg AT mail DOT gmail DOT com> <e4b6f4cd-1fb2-5d4c-1f94-f8ca73bbfa1f AT ferzkopp DOT net> <20180212164945 DOT GA2361 AT jbsupah>
From:	Andreas Schiffler <aschiffler AT ferzkopp DOT net>
Message-ID:	<ec5eb9a0-b33e-5bc8-090d-db0c571d5846@ferzkopp.net>
Date:	Mon, 12 Feb 2018 20:58:28 -0800
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>
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
Note-from-DJ:	This may be spam

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

- Raw text -