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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=WQkAn/AwWszAQqlV6fmG8tZSoq1QkIPBdit7nATHE5UATzdWhZDJk FjL4qt1FRe1qgND07xBZaP4YM6ZPQPqbm69ZSRFPuESuvYXGjeqgj79N3Ea0tEUn bTiD3k5tChHi/qG+ZMVfw9DC8g4WKsudQ4B0rdXnDTDgm2OzQE25s8= 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:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=YqO+2GFuYoeQi8QK+h2bcwQpcxE=; b=OTJ2VzvU2f/yXBQbJ5pbORqeaQSR vnqJvRbxGNHXmZZ6zMiehk65ydG07FTwrdvlqV50aOymzBGQOdASKKbyoRdlMELg 4L1VcZzdfOmr/8E9FqgbTHJWhBOr0tqaz1BvJmUp2bARxFk/jV3nIWQ7mE3rlzgn 7kHs80b1eDZqIQI= 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=-1.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 Date: Thu, 6 Jun 2013 19:27:11 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: ASLR breaks cygwin Message-ID: <20130606172711.GE13320@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <51B0B1F2 DOT 4090402 AT gmail DOT com> <75109671 DOT 20130606204049 AT mtu-net DOT ru> <51B0C178 DOT 1050605 AT etr-usa DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <51B0C178.1050605@etr-usa.com> User-Agent: Mutt/1.5.21 (2010-09-15) On Jun 6 11:06, Warren Young wrote: > 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).) The problem is not the call. Such a call exists, since Vista even one with very simple usage. The problem is that this call has been created for SUA, and some Win32 libs as well as the console subsystem don't work with this call because there never have been made provisions for a fork call in the Win32 libs. Chances for a change are rather low. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- 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