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=aO844PJpSiRVi+fgJX6IrYTGpNy/gIwBeF/8/7HMkdRqQUVLSX7S3 vrHt+NaU5mN+MqXT3MHAkgru9YTvPMphMo8g5mgFkfDKdA94EMTeB9VhUqo/QsKm +Yqb+Zz3aRuazD+tLKKf66+nqTP6D5GkWq0U65eh7ZXnvVG3PwUxE0= 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=QOVzYyHxltgDVAnvjoODIgqD3Ak=; b=AkHpL08VhT1GG3VjlzvlGcClFRN5 Q/E6rXdpjHo6Ead2I60dEITAkxeqxyFj1rCVqmITbzFvZXEFQ8hHbRtZ8XyJ94/O MYbHoN2o+UyL2o6rkQTVPvUdmuLH5g2xN6BFs+JNHg4BMQzeX2yb7eM4xXRxGwXP gskeDRybGFJdRkM= 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 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-101.5 required=5.0 tests=AWL,BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=0x70000000, alsr, WoW64, 0x6b000000 X-HELO: mout.kundenserver.de Date: Mon, 9 Jul 2018 14:37:39 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Fork issue on W10 WOW Message-ID: <20180709123739.GB27673@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <7ad0e0d4-438b-33ad-a711-e0b1996fa6f6 AT gmail DOT com> <20180709090332 DOT GC3111 AT calimero DOT vinschen DOT de> <87e94b8c-13d0-928e-957d-c32b15b8a962 AT gmail DOT com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <87e94b8c-13d0-928e-957d-c32b15b8a962@gmail.com> User-Agent: Mutt/1.9.2 (2017-12-15) --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Jul 9 13:37, Marco Atzeri wrote: > Am 7/9/2018 um 11:03 AM schrieb Corinna Vinschen: > > On Jul 8 18:03, Marco Atzeri wrote: > > > Am 30.06.2018 um 22:47 schrieb Ken Brown: > > > > On 6/30/2018 11:52 AM, Marco Atzeri wrote: > > > >=20 > > > > I've never had this problem with my own 32bit installation on W10, = but I > > > > just reproduced it by doing a new installation with your list of > > > > packages.=C2=A0 Have you tried just installing a minimal list of pa= ckages > > > > that you need for building the packages you maintain? > > > >=20 > > >=20 > > > On a fresh minimal installation the problem can arise again > > >=20 > > > $ cygcheck -cd |wc -l > > > 245 > > >=20 > > > as the first system shared libs are lower than the rebase > > > DefaultBaseAddress=3D0x070000000 > > >=20 > > > 6F810000-6F811000 r--p /cygdrive/c/Windows/System32/wow64.dll > > > 6F811000-6F844000 r-xp /cygdrive/c/Windows/System32/wow64.dll > > >=20 > > > I think that rebase should consider different rebase > > > base address for W10. > > >=20 > > > Using DefaultBaseAddress=3D0x06F000000 seems fine > > > for the time being > >=20 > > I can do that in the rebaseall script (I have a matching patch locally), > > but it looks like a race we can't win in the long run. 240 Megs less > > space is a lot given the number of DLLs in the distro. >=20 > I know, but until we try to support the 32bit version, we need a > way to handle it. >=20 > > To make matters worse, I just checked my local 32 bit W10 and it turns > > out that various Windows DLLs loaded by default (even in a simple tcsh) > > are at even lower addresses, e.g. > >=20 > > 6B690000-6B6A3000 /mnt/c/Windows/System32/netapi32.dll >=20 > I suspect it is due the their 64bit base address netapi32.dll is 32 bit. And it's a 32 bit OS, not WOW64... > $ objdump -x /cygdrive/c/Windows/System32/wow64.dll|grep ImageBase > ImageBase 000000006b000000 >=20 > $ objdump -x /cygdrive/c/Windows/System32/wow64win.dll |grep ImageBase > ImageBase 000000006b180000 >=20 > It is like they put the 64bit System 32 over 0x6b000000 (maybe) 0x6b000000? In your previous mail you wrote 0x6f000000. > and the WoW64 over 0x70000000 I don't think there's a rule. On my 64 bit W10 system: 76E60000-76ED8000 /mnt/c/Windows/System32/wow64win.dll 76EE0000-76EEA000 /mnt/c/Windows/System32/wow64cpu.dll 76EF0000-76F42000 /mnt/c/Windows/System32/wow64.dll Of course you can rebase the wow64 DLLs, it's just unclear if that helps, given Windows uses different DLL addresses for their system DLLs after each reboot. > But I guess that ALSR can play around that numbers. > There is still a way to disable ALSR? ASLR is disabled by default on Cygwin executables. Unless it can't be disabled anymore for certain (system?) DLLs. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAltDVxIACgkQ9TYGna5E T6AQLg//f/LtrB7gBXXGrHoSz+Wbp1oHtscEPIt9EED/Bdx5nLAswq6/OScsCuuR ggfCz6RYxa8fTQlGMpQg/S2RO8bvII8/5QSAUQiEYL5DrUFrRKYlQjUFpDvl1Lsi pw8GY4OqGceyc27/MmLs9N6+Qt0jiwy0VClfLtJ6DlqYjOgzkkhmU9AYKnPECOAI FpkNkjkDjRR0Iz7+tSl/ZbyIOaYH+8TWwqNOWDRfMyvSMk7ojbFK6UdJ0EiG+egB VqL/ZaCgRtvLjkZiWlYi2RjAqYWtRnOmMLV+qMPtgEQOxItYGqI4p1/E/qDPai92 w8zBYDID2o1hDuxLXMCZcYdmpOaV2EMj4C1RUTWsOfcwwAxNo62jQTME3qJY4tMy 7Gin9Imss/YkOJ1BzreZC1lv/UIzLMtrqa2TnRa/xl42s2xYkA9Yz0vbAIaVWfZ5 ej9Uh/cjQkZ5WgaHY8a3/gzH3QZmrniBMS9T4ky3F8mzZ4FD0AAVc3aWl0x6wBEi ZBXHlnFQWfQEQVi0urjIJS7lyXvywNq4w7R/ZMrW+OQI+XT8mWBRlhWYSYnjN15F vDLQ+eKiSEaTHvZrVeDZCKJ9p3+s1ub6h0nmaBQpeWf8ifVLXhzmCQT0IhM6si43 biJJgc6Xe5tfYMIrIilEAkhS0IOZ27w5kbA0GSsT5J0g6mO5bB0= =2FND -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--