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=Vi
	t9FlxHYMIMBqgbyuWGWiFjxnE0p05GJk8cfiALWtTQUTyZWv1qSxCa6PlEYN71Hw
	5Cpk0EhOqBpSj7Ii0YGxJqhVKZy3IOxO6ctjKT2R4dbRtu2EHV3Dcuabd7du92R2
	nJ1PxrLaFKn66uRnDk3hYMeNZmnpeCmUxCNWF+XOE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <524DF640.9080701@cygwin.com>
References: <CAJty3ZxPwByrCu6No2-53vc3QiDXX1G8KZd3RC5K8xBEA4k2ww@mail.gmail.com>	<524DE69B.1090301@cs.utoronto.ca>	<524DF640.9080701@cygwin.com>
Date: Tue, 8 Oct 2013 15:25:46 -0400
Message-ID: <CACUHbYOHSKPrX1JP+_RorxMEe=KZewHbv+uRM2sjsycHQqvjzQ@mail.gmail.com>
Subject: Re: fixing BLODA-caused fork failures
From: David Boyce <dsb@boyski.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1

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

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