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
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <525460FE.3090403@cs.utoronto.ca>
Date: Tue, 08 Oct 2013 15:46:06 -0400
From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
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@cygwin.com
Subject: Re: fixing BLODA-caused fork failures
References: <CAJty3ZxPwByrCu6No2-53vc3QiDXX1G8KZd3RC5K8xBEA4k2ww@mail.gmail.com> <524DE69B.1090301@cs.utoronto.ca>	<524DF640.9080701@cygwin.com> <CACUHbYOHSKPrX1JP+_RorxMEe=KZewHbv+uRM2sjsycHQqvjzQ@mail.gmail.com> <52545E28.40803@cygwin.com>
In-Reply-To: <52545E28.40803@cygwin.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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