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:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=tBjltud5irDEs7nSYHI/dhz0kQu2w/OaMSop/j1YoKP QAws3hmVrJF2y8s32UV88RE0WHcyeddW3Nrw+cQ+CA4h0STn1HMRjW+A0tzhGRmy 3lnyX8rsxzG6w/JbLpN3l/qVSZd7/YC2lz07XaHDJmCMMjzA9m5KbqxXxdeM3BBo = 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:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=PJq5K5ygnj23wnEb2WqWdCfzsQM=; b=FjjEM5L/ujtesgavK opgEVfOCaGTT/C7He74HdT/BaoifdU2ygiblZZbwrLdxHxz2wpjRjlK0Eo7NwStj 9NTK2pyRRYmXr+kA7D+1jSuKK1wr2sP0af2gMStnNwDr5BRy6f9hrUyCtQjLZOuE b0rKloG98Cy+2MpmHbcYIcI78E= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-3.0 required=5.0 tests=AWL,BAYES_20,KHOP_THREADED,RP_MATCHES_RCVD autolearn=ham version=3.3.1 Message-ID: <51B0C178.1050605@etr-usa.com> Date: Thu, 06 Jun 2013 11:06:00 -0600 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Cygwin-L Subject: Re: ASLR breaks cygwin References: <51B0B1F2 DOT 4090402 AT gmail DOT com> <75109671 DOT 20130606204049 AT mtu-net DOT ru> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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[1] and the need for a separate native POSIX API is gone[2]. 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).) [1] http://goo.gl/4hrPg [2] Presumably, gone with the 90's, when government contracts would sometimes require POSIX compatibility. -- 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