From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Windows10 Creators Update
Date: Mon, 17 Jul 2017 08:31:00 -0000 [thread overview]
Message-ID: <20170717083045.GB14583@calimero.vinschen.de> (raw)
In-Reply-To: <20170717080933.GA14583@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]
On Jul 17 10:09, Corinna Vinschen wrote:
> On Jul 16 11:10, Achim Gratz wrote:
> > Achim Gratz writes:
> > > I've finally got that update installed on my Windows10 box and sure
> > > enough I immediately got fork problems (on 32bit only). Since this
> > > update the WoW64 DLLs get mapped below 0x70000000:
> >
> > …and on each reboot these end up somewhere else, sometimes even above
> > 0x7000000 as intended.
>
> It seems the Windows team raised the size of the ASLR pool on 32 bit, at
> least on wow64.
>
> > > In all likelyhood that means we can't really support 32bit on Windows 10
> > > anymore unless there's a way to stabilize the addresses used by these
> > > DLL and then teaching rebaselst to rebase from a lower starting point.
> >
> > Or we will have to ask our users to reboot more often. :-(
>
> Sounds like a plan.
>
> On Wow64 we have the upper 2 Gigs address space for us, but I vaguely
> recall that there was a problem moving the DLLs into this area. That's
> why we only have heap and mmap there these days. Maybe we should
> reconsider...
>
> But, then again, what's the lowest address for the wow64 DLLs you
> observed? And what about native 32 bit (no wow64 DLLs)?
On native 32 bit:
6B1E0000-6B1E1000 r--p 00000000 5A70:6C49 2814749767187753 /cygdrive/c/Windows/System32/winrnr.dll
> We can't stabilize the address for the Windows DLLs, but we
> can obviously adapt to it by changing rebase.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-07-17 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 8:36 Achim Gratz
2017-07-16 9:10 ` Achim Gratz
2017-07-17 8:09 ` Corinna Vinschen
2017-07-17 8:31 ` Corinna Vinschen [this message]
2017-07-17 17:41 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170717083045.GB14583@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).