X-Recipient: archive-cygwin AT delorie DOT 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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=Hb jmDoMcXEAKXchB4jbR2gFhWlfdvMCsaNXw6/k9hX0FqN0Xvn79hw6dB7NvULo58Q bsz5+SSWsSqYaW0Yo8yVPefVZ3zYgbtD0fNI+udoGgsWx8/oU30VbYUORjQlEZMO 0QUA6998iE0Nt8SICowviBa/SB4JUAy7isiCxQiTg= 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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=t7rYnDwr zaSn5ONCBcZBrNgC8AI=; b=BTookX6G6OfGtgFNkCVUe16C4KPqFcEXMPycRYtv j+gquVGxFVZf+p8AEPIITJXC2TYCL2rqp9rEnP5ay6Ci9L9tpEF7Pf0HG36+S45U C1a3Ih/aeqmOF1J3Eebe8EzHo7dmby7hrO/8ngqCKgDnFn8A1Ebs7vk7t/5CCf5p VyU= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=AWL,BAYES_50,KAM_INFOUSMEBIZ,SPF_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: alum-mailsec-scanner-2.mit.edu MIME-Version: 1.0 X-Received: by 10.107.129.218 with SMTP id l87mr25512013ioi.181.1446513898505; Mon, 02 Nov 2015 17:24:58 -0800 (PST) In-Reply-To: <20151102113113.GD5319@calimero.vinschen.de> References: <20151102113113 DOT GD5319 AT calimero DOT vinschen DOT de> Date: Mon, 2 Nov 2015 18:24:58 -0700 Message-ID: Subject: Re: Help: cygheap base mismatch detected From: Jim Reisert AD1C To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes On Mon, Nov 2, 2015 at 4:31 AM, Corinna Vinschen wrote: > 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. I meant to reply to this earlier today, but lines between day/night and work/not have been too blurry lately. I tried a clean install of 32-bit Cygwin, but that didn't fix anything. So then on a lark, I rebooted the computer (turned it off actually, which I have not done in weeks), and magically, the problem went away. Maybe Windows 10 had its knickers in a twist or something, but everything else seemed to run just fine, except Cygwin. I have tried 64-bit Cygwin in the past. I do a lot of file I/O and sorting/searching on largish test-based data sets, and 64-bit was noticeably slower than 32-bit Cygwin, so I have not been gung-ho to switch. Maybe now that it's more mature, I should give it another shot. -- Jim Reisert AD1C, , http://www.ad1c.us -- 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