This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: fixing BLODA-caused fork failures
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 08 Oct 2013 15:34:00 -0400
- Subject: Re: fixing BLODA-caused fork failures
- Authentication-results: sourceware.org; auth=none
- 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>
- Reply-to: cygwin at cygwin dot 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