X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_YG
X-Spam-Check-By:	sourceware.org
Received-SPF:	pass (google.com: domain of marco DOT atzeri AT gmail DOT com designates 10.236.72.170 as permitted sender) client-ip=10.236.72.170;
Authentication-Results:	mr.google.com; spf=pass (google.com: domain of marco DOT atzeri AT gmail DOT com designates 10.236.72.170 as permitted sender) smtp.mail=marco DOT atzeri AT gmail DOT com; dkim=pass header.i=marco DOT atzeri AT gmail DOT com
MIME-Version:	1.0
In-Reply-To:	<20120301105139.GF2257@calimero.vinschen.de>
References:	<4F4E7CC8 DOT 9090804 AT cwilson DOT fastmail DOT fm> <20120301105139 DOT GF2257 AT calimero DOT vinschen DOT de>
Date:	Thu, 1 Mar 2012 11:59:42 +0100
Message-ID:	<CAB8Xom9nR9g=R_uzzZM5D+OHZ3wQhkJ+F5tAKBL0xL60iTc9rA@mail.gmail.com>
Subject:	Re: cygheap base mismatch detected
From:	marco atzeri <marco DOT atzeri AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id q21B039i030393

On Thu, Mar 1, 2012 at 11:51 AM, Corinna Vinschen wrote:
> On Feb 29 14:30, Charles Wilson wrote:
>> I've been running into a strange "error" lately (that is, I first
>> noticed it for sure on 1.7.10, but it MIGHT have occurred also on 1.7.9.
>> It persists on 1.7.11). cygcheck -- and *only* cygcheck -- is reporting
>> a cygheap base mismatch but only on an XP64 machine:
>>
>> $ cygcheck -cd cygwin
>>       1 [main] cygcheck (3756) C:\cygwin\bin\cygcheck.exe: *** fatal
>> error - cygheap base mismatch detected - 0x61270870/0x2170870.
>> 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.
>> Cygwin Package Information
>> Package              Version
>> cygwin               1.7.11-1
>>
>> (Note that cygcheck actually *does* complete the requested command,
>> after the error message from (cygwin1.dll/dcrt0.cc?) is printed.
>
> Very strange.  For two reasons.  First of all, why is the mismatch
> message printed at all?  The code in question is basically:
>
>  if (res->cygheap != (void *) &_cygheap_start)
>    multiple_cygwin_problem (...);

0x61270870 != 0x2170870

>
> But res->cygheap and &_cygheap_start are apparently identical, so why
> is multiple_cygwin_problem called?
>
> And then multiple_cygwin_problem calls api_fatal to print the message
> which means that ultimately TerminateProcess() is called.
>
> I tried that on my XP64 test machine and cygcheck worked fine.
>
> Could you do a parallel installation on the same machine and see how it
> behaves there?
>
>
> Corinna
>

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