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=KohKkCDlbGtN9ydl
	b+MQU5UPif454HVug1xAEXX6tpzZehGV+ia9Vi6LWUXzsVEH+mMmPxHFcwyczViU
	XStm37sWzlTPJRf2gJRtfO9V+nL2sFne6cCAYke98lWOiC/f7eh/rM//ZMQpjXu0
	4ZG9oHuKrwcsaf6PTF+sZIJp9/s=
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=YKHpNriqeQ9OkVVxc28ucY
	nEbHs=; b=w4WOx/7vQiB7D1KJDxeTXqgMbMHt8co5Y8JJlCoCHLeIqDCc6AsKWK
	cIav3rV2Kyp5kirvUckWrQ0supbd3skYBYpoeHLlC9kD3gATKU+qTufi7exeBv8c
	YLirSKjCUR3K88J34gj2LQeuUVdtGtWnOj31hT0k90gFaFWcARgKs=
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_40,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=H*Ad:U*mark, H*MI:sk:DM2PR02, H*r:8.12.11, H*F:U*mark
X-HELO:	m0.truegem.net
Subject:	Re: Advice for debugging heap mismatches? (Win10 Insider build 14926)
To:	cygwin AT cygwin DOT com
References:	<DM2PR0201MB079977535C2477CA6B0EF745A7F30 AT DM2PR0201MB0799 DOT namprd02 DOT prod DOT outlook DOT com> <DM2PR0201MB07990C9272767BC3A62529C2A7CB0 AT DM2PR0201MB0799 DOT namprd02 DOT prod DOT outlook DOT com> <57E700EA DOT 2040802 AT maxrnd DOT com> <DM2PR0201MB079975A16D4E98A8B20250EEA7CC0 AT DM2PR0201MB0799 DOT namprd02 DOT prod DOT outlook DOT com> <DM2PR0201MB079958F9EBD05C7DED300E16A7C30 AT DM2PR0201MB0799 DOT namprd02 DOT prod DOT outlook DOT com> <57F0D486 DOT 1060301 AT maxrnd DOT com> <DM2PR0201MB07991C4D55AD240A54BA9E65A7C30 AT DM2PR0201MB0799 DOT namprd02 DOT prod DOT outlook DOT com> <DM2PR0201MB0799F93894D9F5E334A69789A7C30 AT DM2PR0201MB0799 DOT namprd02 DOT prod DOT outlook DOT com>
From:	Mark Geisert <mark AT maxrnd DOT com>
Message-ID:	<57F1FD3E.80601@maxrnd.com>
Date:	Sun, 2 Oct 2016 23:39:58 -0700
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40
MIME-Version:	1.0
In-Reply-To:	<DM2PR0201MB0799F93894D9F5E334A69789A7C30@DM2PR0201MB0799.namprd02.prod.outlook.com>

Tony Kelman wrote:
>> You've got two different cygwin1.dll somewhere on your PATH.
>
> For more information, I have one cygwin64 installation on C:, one
> cygwin32 installation on E:, and they're never both on my path at
> the same time. I'm not sure where that orphan registry entry that was
> showing up in cygcheck.out came from, but I removed it and it made no
> difference.

With only one Cygwin installation on C: I can only come up with wild guesses. 
Are you somehow alternating between the C: and E: Cygwin versions, or running 
them simultaneously from separate windows, or accidentally running 32-bit Cygwin 
commands from a 64-bit Cygwin terminal window?  Unusual stuff like that?

One sure-fire way to make sure your 32-bit E: installation is not causing havoc 
with your 64-bit C: installation is to temporarily rename E:\cygwin32 to 
E:\somethingelse and retry your build.  This should not be necessary but I don't 
know what else to suggest.

I have in the past run 32-bit and 64-bit Cygwin installations simultaneously on 
the same machine, in order to build 32-bit and 64-bit Cygwin DLLs at the same 
time.  Never had a problem.  But that was Windows 7 so probably not applicable.

> This is absolutely due to a change in Windows itself. 3 updates in
> a row now, 14926, 14931, and now 14936, it's 100% reproducible just
> from updating Windows. Downgrading to build 14915 gets everything back
> working again, but that build is now expired so the only way for me to
> get back to a supported build of Windows where cygwin works properly
> is by totally reinstalling Windows. I haven't done that yet, but if
> we can't identify the problem and a solution soon, I will have to.

I see what you've been saying about different insider builds of Windows 10 but I 
don't think anybody here is beating up on these releases.

..mark

--
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 -