From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Fork issue on W10 WOW
Date: Sat, 14 Jul 2018 17:58:00 -0000 [thread overview]
Message-ID: <874lh17txr.fsf@Rainer.invalid> (raw)
In-Reply-To: <c1aa10ad-e685-f232-6719-5c653f747f83@gmail.com> (Marco Atzeri's message of "Thu, 12 Jul 2018 18:35:12 +0200")
Marco Atzeri writes:
> currently I have over 73000000 always busy
> 73C50000-73C51000 /cygdrive/c/Windows/SysWOW64/cryptbase.dll
What type of Windows do you use? I have Home N for testing at home and
Server 2016 plus a bunch of users w/ Enterprise clients (will get one
myself in a few days) and never seen any such problems.
>> You could reboot the machine until the DLLs are at an adddress you
>> can work with and then never reboot again. /duck/
>
> Feasible, just time consuming..
> It took a dozen trials before reaching a nice
>
> 71D10000-71D11000 /cygdrive/c/Windows/System32/wow64.dll
>
> the last lottery numbers were:
>
> 5A9B0000-5A9B1000
> 66AB0000-66AB1000
> 53DA0000-53DA1000
> 6A470000-6A471000
> 6DBF0000-6DBF1000
> 5F020000-5F021000
> 680D0000-680D1000
> 52650000-52651000
> 71D10000-71D11000
>
> Now I am stuck to German system and never
> restart. Until next MS patch day...
Are you using one of the preview update channels or did you use one in
the past? Leading up to 1803 MS has apparently tested some new ASLR
tricks and I don't think they change the settings back to default even
when you are later switching back to a "normal" release version.
Anyway, with 1803 there is a setting now in the security panel somewhere
that forces ASLR to be used even when the PE flags say otherwise. I
don't know if that can be switched on just for the WoW64 subsystem, but
it would probably be something you can do via group policy (on a Pro or
Enterprise client).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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
next prev parent reply other threads:[~2018-07-14 14:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 17:33 Marco Atzeri
[not found] ` <c1505248-8d03-c0b6-37ca-9c6eed2100e9@cornell.edu>
2018-07-01 8:51 ` Marco Atzeri
2018-07-08 16:03 ` Marco Atzeri
2018-07-09 9:03 ` Corinna Vinschen
2018-07-09 11:37 ` Marco Atzeri
2018-07-09 12:37 ` Corinna Vinschen
2018-07-10 5:33 ` Marco Atzeri
2018-07-12 12:34 ` marco atzeri
2018-07-14 12:46 ` Corinna Vinschen
2018-07-14 14:31 ` Marco Atzeri
2018-07-14 17:58 ` Achim Gratz [this message]
2018-07-14 19:03 ` Marco Atzeri
2018-07-14 22:41 ` Achim Gratz
2018-07-15 2:12 ` Brian Inglis
2018-07-15 9:18 ` Marco Atzeri
2018-07-15 13:25 ` Achim Gratz
2018-07-15 19:33 ` Brian Inglis
2018-07-15 23:01 ` David Stacey
2018-07-16 18:58 ` Marco Atzeri
2018-07-16 1:06 ` Andrey Repin
2018-07-17 18:34 ` Marco Atzeri
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=874lh17txr.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@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).