From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 66537 invoked by alias); 3 Oct 2016 06:40:12 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 66527 invoked by uid 89); 3 Oct 2016 06:40:11 -0000 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 Received: from m0.truegem.net (HELO m0.truegem.net) (69.55.228.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 03 Oct 2016 06:40:08 +0000 Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id u936e7Pw052972 for ; Sun, 2 Oct 2016 23:40:07 -0700 (PDT) (envelope-from mark@maxrnd.com) Received: from 76-217-5-154.lightspeed.irvnca.sbcglobal.net(76.217.5.154), claiming to be "[192.168.1.100]" via SMTP by m0.truegem.net, id smtpdn8csQJ; Sun Oct 2 23:39:58 2016 Subject: Re: Advice for debugging heap mismatches? (Win10 Insider build 14926) To: cygwin@cygwin.com References: <57E700EA.2040802@maxrnd.com> <57F0D486.1060301@maxrnd.com> From: Mark Geisert Message-ID: <57F1FD3E.80601@maxrnd.com> Date: Mon, 03 Oct 2016 06:57:00 -0000 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: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2016-10/txt/msg00036.txt.bz2 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