DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=jTC7incjpa2tcuMBk1xUgbbPFEKe0vTi0salzDkWkC2/aiI+FRANt
	9z28svBQ0KbHKtwmVeMY/nawDiCCVhbMG2nqkekLLQZLzQIAc3LOIHEw4vmRetCl
	tFY8cpxZbE1l27/Pdh0kmm65WIpkkqZwwZY412/Eb18bbbKTezt3Hs=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Mon, 2 Nov 2015 12:31:13 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Help: cygheap base mismatch detected
Message-ID: <20151102113113.GD5319@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CAK-n8j6UevHpRwpRcDoSESuaXXeBzG6tF0xqDphmaO7JCLEPiA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="KXWI/Lwc0/Thrskm"
Content-Disposition: inline
In-Reply-To: <CAK-n8j6UevHpRwpRcDoSESuaXXeBzG6tF0xqDphmaO7JCLEPiA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

--KXWI/Lwc0/Thrskm
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Nov  1 17:22, Jim Reisert AD1C wrote:
> I installed the latest Windows 10 update this morning and rebooted.
> Now Cygwin won't work at all.  Using the latest test release of
> Cygwin:
>=20
> CYGWIN_NT-10.0-WOW JJR 2.3.0(0.291/5/3) 2015-10-22 17:54 i686 Cygwin
>=20
> Any ideas?
>=20
> F:\>dash
> $  rebase-trigger fullrebase
>       0 [main] dash (4564) C:\Cygwin\bin\dash.exe: *** fatal error -
> cygheap base mismatch detected - 0xABB400/0xD1B400.

*Both* addresses are wrong.  The 32 bit Cygwin DLL has to be loaded to
address 0x61000000 (as noted in the file header) which, if done correctly,
results in a cygheap address > 0x61000000.  The cygheap is part of the
DLL binary, so it's loaded with it.  In Cygwin 2.2.1, the address should
be in the 0x612fc000 range.

It seems a Windows DLL or a virus scanner DLL gets loaded to this
address for some reason.  I'm a bit at a loss to make a suggestion here,
except for switching to 64 bit Cygwin which has much less problems with
this due to the huge address space.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--KXWI/Lwc0/Thrskm
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWN0mBAAoJEPU2Bp2uRE+g7NkP/0FBPJIg1sUC67r+iS5KY/Xo
JTRJ6Svj0cqYDMZ3OCg4nKkcu8mk+tkA0bfnikPygd6rgjl257M7HeZXDhPUFUsA
Ja488YGwgmwnOgud5dyMaYGuGhtm0TF4jVbOOaDCFb4EmBXDG3nvOtkCXX3tiV7o
+1XdlBTSQQ34snm9Ps5Kkf95hY9GWDb14J8mYI4LcThgorqKOvjpX+3uT6brhf0V
5qJgUBFkTCPRtWNyV/XktNDgjD5zOSYS51pOL9+DpSl7PFSydm4RxHuZYUtiyfcc
s03cAlO+fh3OLFUcyDrCFPSv2S6GjHdfBic1lDSQy74xQSfEnYhbl6uU9RolnQta
xELttlmjMAs1v8OjhgbnDsIWjP+H2wnYoy9sjd7/uZRWDU38Y5iAJ2zU8S5PFXNa
lXbOmh3fzmS6FKf0TBxtrzahdshfJ9uSxJ7QgvmM7SnyIIdkwHnVOG//KjaDRWPU
W2uh7ojTC6NZj3wEfili4qhM3ClSIogmF5bm52g2Ws5vNfiW2NwjTx8XxTGMJB4c
0ECRqcbmUV0EZqYRToZamj4uvk7rMKPz2efKzUvx6spWhnrsN6O7cEj8JSULf+oS
fmULRvucvfqqr9ltOuWjawvqad8SEP05TbJnhBfDXdAMe1WVSYGnizx9hmrVx8Ck
3T8MFsOLJh/M28VWXIUf
=bCkO
-----END PGP SIGNATURE-----

--KXWI/Lwc0/Thrskm--