From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 114846 invoked by alias); 24 Sep 2016 22:40:50 -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 114835 invoked by uid 89); 24 Sep 2016 22:40:49 -0000 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, anybody, H*r:8.12.11, expire 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; Sat, 24 Sep 2016 22:40:48 +0000 Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id u8OMelDX042333 for ; Sat, 24 Sep 2016 15:40:47 -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 smtpdM5LwOy; Sat Sep 24 15:40:42 2016 Subject: Re: Advice for debugging heap mismatches? (Win10 Insider build 14926) To: cygwin@cygwin.com References: From: Mark Geisert Message-ID: <57E700EA.2040802@maxrnd.com> Date: Sun, 25 Sep 2016 08:20: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-09/txt/msg00317.txt.bz2 Tony Kelman wrote: >> I've tried manually rebasing, setting rebase-trigger, rerunning latest >> setup, rebooting, etc. During big parallel makes none of the above helped >> with getting rid of intermittent heap mismatch errors during fork after I >> upgraded to Windows 10 Insider build 14926. I had been on the Insider fast >> ring for a few months > > Anybody? Just checked 14931 and it has the same problem. > I'll be switching back the slow ring as soon as it lets me, but > I'm about to start getting "build will expire" popups. You're absolutely sure your rebasing operations are being done without any Cygwin processes running, even background cygserver, sshd, etc? Could you paste a complete sample of the error message so we can determine where in the Cygwin code it's coming from? ..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