From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 92821 invoked by alias); 12 Jul 2018 10:31:41 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 92806 invoked by uid 89); 12 Jul 2018 10:31:40 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:932 X-HELO: mail-wr1-f50.google.com Received: from mail-wr1-f50.google.com (HELO mail-wr1-f50.google.com) (209.85.221.50) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 12 Jul 2018 10:31:38 +0000 Received: by mail-wr1-f50.google.com with SMTP id m1-v6so8438278wrg.5 for ; Thu, 12 Jul 2018 03:31:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=QblFrrj91zIhcM5Vc5/TkVfVC9VybLZjyCiFVWLlre0=; b=pc03uly+6FT+hR5ucoHvv29C29gIx6eGY2tKbeaknMOMJC/06mGg7sgXDbpNxiKsot TNUBXAst8ugm+htJHKQ5pH4ov/RF2KeqFTJ3CumqvKC4X3tR0ByU8S5+LOARi4w1wZER R52VsXL40gLyuLB86pTsR4tShEJJ3/HtQFSU3npHvLQL6dwy0yXJAFEfl2ZhX+XJRqDD gjY4hbDkSbLM+qy7gasUPJCkeYBUeIJJNPHJ+NRxeEPEkcVyzj6PIqqKNXZfBhj8dco2 LTyI6N8+Ap09MCrOw6LvNp7xYILzXp8oZQFmHr/GcEP91Meqq9yPlA/Z84OKXfTkjatW Llow== MIME-Version: 1.0 Received: by 2002:adf:b3d4:0:0:0:0:0 with HTTP; Thu, 12 Jul 2018 03:31:36 -0700 (PDT) In-Reply-To: References: <7ad0e0d4-438b-33ad-a711-e0b1996fa6f6@gmail.com> <20180709090332.GC3111@calimero.vinschen.de> <87e94b8c-13d0-928e-957d-c32b15b8a962@gmail.com> <20180709123739.GB27673@calimero.vinschen.de> From: marco atzeri Date: Thu, 12 Jul 2018 12:34:00 -0000 Message-ID: Subject: Re: Fork issue on W10 WOW To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-07/txt/msg00124.txt.bz2 On Tue, Jul 10, 2018 at 7:33 AM, Marco Atzeri wrote: > Am 09.07.2018 um 14:37 schrieb Corinna Vinschen: > > > It seems there is some type of ASLR for the wow64. > I will try to rebase using 0x6b000000 to see if > make any change > from my experiments the 32bit under W10 is substantially unusable. At every restart the base address of the wow64*.dll are moved randomly everywhere between 0x50000000 and 0x70000000. It seems the 32bit subsystem is totally ignoring that cygwin programs have not the ASLR flag. May be the subsystem base address is initialized before any cygwin program is started. It seems I have only two choices: - disable totally ASLR, but some guidance (1) around seem not working anymore - use a virtual machine for a 32 bit W7 system to be used as build environment. Any suggestion for the two approaches ? Regards Marco 1) https://gist.github.com/trietptm/b84ccad9db01f459ac7e -- 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