This is the mail archive of the
mailing list for the Cygwin project.
Re: ASLR breaks cygwin
- From: Warren Young <warren at etr-usa dot com>
- To: Cygwin-L <cygwin at cygwin dot com>
- Date: Thu, 06 Jun 2013 11:06:00 -0600
- Subject: Re: ASLR breaks cygwin
- References: <51B0B1F2 dot 4090402 at gmail dot com> <75109671 dot 20130606204049 at mtu-net dot ru> <CAPF-yOYFoZ6sjJgFEEg2hZ5zJSE4eP9mE3-+_NSifxgnyii8tQ at mail dot gmail dot com>
On 6/6/2013 10:52, Dan Kegel wrote:
I wonder if we could get them to recognize the parent-child
relationship somehow, and keep the same address space
in the child.
Just kidding. Hell would sooner freeze over.
I don't know about that. For a long time, they had a bigger conflict of
interest with Cygwin due to SFU/SUA/Interix and the POSIX subsystem.
They announced SUA's doom a couple of years ago and the need for a
separate native POSIX API is gone. I even recall reading on this
list that Microsoft now recommends Cygwin, at least unofficially.
Perhaps Microsoft now has some incentive to create a native fork(2) like
call in their OS that Cygwin could use. (Or something close enough,
like Linux's clone(2).)
 Presumably, gone with the 90's, when government contracts would
sometimes require POSIX compatibility.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple