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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=w/v22DwzE91LTQGxdB6KnhnPnhURAu96g7EFEtX6WWr eO6WCfvI+yu4A7L8AwwbqwrsICdIYNSYTGGjss4DNJXmtNRSjM6G3wNq5gwAnYfa /kZezS4RVpy7sVzHc7s4FWjDyw37trJToQ4HuotXeFv0X0XoSVrbVwZN7I0eYQ+0 = 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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=U9XWGL+tJtX/C0Mk5YHN7XBiiEo=; b=Pp83GgyZULXBmySU/ Pl/DxVAYEpy494hZKA3c/eO1+TBC1MATN/H0Z6g7+YMICQSO0nekoHE2RooMX/E5 UTXlR1paHhSdZAaSQbeCEcy6e48Bm6JPljIKKY3nIsh6W9i16yHFiQaF1aoemxqe JMfgCMcdQ1d+ipWBC8F4mMOQtk= 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-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_NEUTRAL autolearn=ham version=3.3.2 X-HELO: bureau84.ns.utoronto.ca Message-ID: <525460FE.3090403@cs.utoronto.ca> Date: Tue, 08 Oct 2013 15:46:06 -0400 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: fixing BLODA-caused fork failures References: <524DE69B DOT 1090301 AT cs DOT utoronto DOT ca> <524DF640 DOT 9080701 AT cygwin DOT com> <52545E28 DOT 40803 AT cygwin DOT com> In-Reply-To: <52545E28.40803@cygwin.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 08/10/2013 3:34 PM, Larry Hall (Cygwin) wrote: > On 10/8/2013 3:25 PM, David Boyce wrote: >>> But as a point of practicality, 64-bit Cygwin can help with some >>> cases of >>> DLL address space collisions. So if you haven't experimented with >>> 64-bit Cygwin in your environment, it may be worth your time. >> >> This sounds very reasonable but I'm curious: is it to date just a >> theory that makes sense or have there been actual reports of 64-bit >> Cygwin solving address-space collisions? > > Solving? Well no. It won't "solve" address-space collisions. But the > larger address space means that there's less chance of the O/S picking > the address your DLL wants for another. No guarentees of course. ;-) > One data point: I managed to make it a few weeks from a clean win64/cygwin64 install to the first BLODA symptoms, even though Windows Defender was alive and well that whole time. Once it hit, though, there was no obvoius way out except to disable WD. Rebooting might also help, by resetting an especially unfriendly ASLR arrangement. Ryan -- 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