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=lihLsRtoHWvPMT59
	MEN3xqh4jEORCz/VmIfkTvdLGuKl3i+joQH25m5JsTS2z08rhwLBulMn6iAFXOuU
	zV0QqestrsRLjj9YJojWAQUcxd0Bk/A14fWKHasJKTrVKBGwo3T/J8pRt0+3nKOB
	eB/fbcSyMTaX67sK8Gwz0H75Jd4=
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=tNbSVIQ1/OUTbqgUO/wfS0
	XpHos=; b=SynnrGfP5DjOEJgpbAOePKDg1UowpmuJ5nnOo2PfxrMX7ViSLOeBrn
	6+uu6PRf0E6qXBhw7HjrB/gaHxndmQmS6ivM/lNJhbmk01jkel+SvLEht/YUAbkv
	lVW322kjsyKOgY+vf+1k63LgHpn+4wwEnW1FCgVteTIYhWsSEZftY=
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=1.6 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=H*Ad:U*mark, listings, insider, mismatches
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>
From:	Mark Geisert <mark AT maxrnd DOT com>
Message-ID:	<57F0D486.1060301@maxrnd.com>
Date:	Sun, 2 Oct 2016 02:33: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:	<DM2PR0201MB079958F9EBD05C7DED300E16A7C30@DM2PR0201MB0799.namprd02.prod.outlook.com>

Tony Kelman wrote:
>> Could you paste a complete sample of the error message so we can
>> determine where in the Cygwin code it's coming from?
>
> Still a problem in 14936. Folks, this could be very bad. Anyone at all
> testing the insider builds, or are we going to be blindsided when an
> update goes out to everyone that breaks cygwin?
>
> Here's one:
>
>        1 [main] cp (6432) C:\cygwin64\bin\cp.exe: *** fatal error - cygheap base
          mismatch detected - 0x180302408/0xD92408.
> 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.

OK, you're seeing two different problems. Solving the one above is critical. It 
might help solve the other problem shown below; we'll have to see.

You've got two different cygwin1.dll somewhere on your PATH. As your builds 
proceed, they likely start out using the correct cygwin1.dll but sometimes load 
the wrong cygwin1.dll along the way. The error message tells you how to solve 
the problem. But I usually use this method:
     - open a Command Prompt running as Administrator
     - cd c:\ or wherever the root of your Cygwin installation drive is
     - dir /S cygwin1.dll
You might see multiple listings of the same cygwin1.dll due to the crazy WoW 
support but these will all have the same date and size. You want to find the 
cygwin1.dll that has a different date (probably older) and size. That's the 
problematic one; rename it or delete it.

Then try running your build again.

>
>
> And another:
>
>        0 [main] cmake 10384 child_info_fork::abort: C:\cygwin64\bin\cygintl-8.dll:
          Loaded to different address: parent(0x3E3680000) != child(0x190000)

This is a garden-variety fork() failure due to the child having something in its 
address space at 0x3E3680000 such that Cygwin can't load cygintl-8.dll at that 
address where the parent has it. But since you've apparently got two Cygwin 
installations on your PATH, maybe that's complicating things. See if fixing the 
first problem above makes this problem go away too.

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