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:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=QhC7G2FoMbYhWiI9
	wiOlAV7fbtPdvFDw13bEXlSt/XazwlmVdzBG9V1i8DN7gJA15GHO/0tBsZI9MtBg
	u2xsoVM1NXfOo9nRXvACB8wg50wCU3FvGheksyESVfg1r8cOmltNo4O6zVLRvZf+
	5m4ZlqD5Qk+t8F6s0G3SpIhVY0I=
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:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=H3wM4pswn0voNXiahVtX+M
	pHdLE=; b=hvX+w9f5Tj/G0dl+gGwjLs69BnZE++I8zHL3e/dxTtSFQQTdxqwi9E
	2cf3ujUdCOEj5ri936wg8a9FC9wzZX+iGv0CxqjxIjo2K8/zWwCKYNKs3aDOowXW
	jPf7WzB84yapedNx4u0MTo4zhZDJElIStiToraeofoWqWMcbfFK2c=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	vms173001pub.verizon.net
Message-id:	<52545E28.40803@cygwin.com>
Date:	Tue, 08 Oct 2013 15:34:00 -0400
From:	"Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: fixing BLODA-caused fork failures
References:	<CAJty3ZxPwByrCu6No2-53vc3QiDXX1G8KZd3RC5K8xBEA4k2ww AT mail DOT gmail DOT com> <524DE69B DOT 1090301 AT cs DOT utoronto DOT ca> <524DF640 DOT 9080701 AT cygwin DOT com> <CACUHbYOHSKPrX1JP+_RorxMEe=KZewHbv+uRM2sjsycHQqvjzQ AT mail DOT gmail DOT com>
In-reply-to:	<CACUHbYOHSKPrX1JP+_RorxMEe=KZewHbv+uRM2sjsycHQqvjzQ@mail.gmail.com>

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. ;-)

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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

- Raw text -