X-Recipient: archive-cygwin@delorie.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:from:to:subject:references:date:in-reply-to :message-id:mime-version:content-type; q=dns; s=default; b=FP+1n qgYpFSg9evWByAPkiaXCz9VLjlwUbWQmYP+lcgPcqfgdJX5eSArEE0Ci70wmqb7D ZfE+VVsG4D9hcLCLcdoDodrIy32Xiqckdz9yqEDX1S8XwXoq/CVBXCLo7hgfM1Pd oUhBChH75XIX/f5+kmqSpk2p+DJlSrAw4qQkMA= 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:from:to:subject:references:date:in-reply-to :message-id:mime-version:content-type; s=default; bh=6sao8xb79d6 12egIfpHXy5HD37w=; b=rv/WGjAC4PHpxP2w7DFhUyhO3NHOSVv12c6mEP59fXz NLbSiS51xgSLCN/byJFl7wn3IlESnucY7Jg5psZU0vaW15QoEEbR/MCo7LBAHYlm mvJxY7rNUX2jkfAonU7wmurhzvZFh87dnDcgEbxELvnQj6iVRk4G+bmHlgcJpNdA = Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mail-in-05.arcor-online.net X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-16.arcor-online.net 3sn3jv6slTz5JYX From: Achim Gratz To: cygwin@cygwin.com Subject: Re: Advice for debugging heap mismatches? (Win10 Insider build 14926) References: <57E700EA.2040802@maxrnd.com> Date: Sun, 02 Oct 2016 14:03:47 +0200 In-Reply-To: (Tony Kelman's message of "Sun, 2 Oct 2016 06:55:25 +0000") Message-ID: <87r37z3ql8.fsf@Rainer.invalid> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Tony Kelman writes: >> 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? How about you start with a sane PATH that doesn#t contain all the Windows stuff? Set a system variable CYGWIN_NOWINPATH=true and try again. > 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. Something occupies the heap area for Cygwin, based on the low address. What does /proc/self/maps tell you? > And another: > > 0 [main] cmake 10384 child_info_fork::abort: C:\cygwin64\bin\cygintl-8.dll: Loaded to different address: parent(0x3E3680000) != child(0x190000) Again either an address collision or some BLODA intercepting the DLL, check the memory maps to see what might be going on. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs -- 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