From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Fork issue on W10 WOW
Date: Sat, 14 Jul 2018 14:31:00 -0000 [thread overview]
Message-ID: <c1aa10ad-e685-f232-6719-5c653f747f83@gmail.com> (raw)
In-Reply-To: <20180712133847.GT27673@calimero.vinschen.de>
Am 12.07.2018 um 15:38 schrieb Corinna Vinschen:
> On Jul 12 12:31, marco atzeri wrote:
>>
>> 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.
>
> Actually, as I wrote before, in my case the wow64 stuff is beyond
> 0x70000000:
>
> 76E90000-76F08000 /mnt/c/Windows/System32/wow64win.dll
> 76F10000-76F62000 /mnt/c/Windows/System32/wow64.dll
> 76F70000-76F7A000 /mnt/c/Windows/System32/wow64cpu.dll
something very nice on your system :-)
currently I have over 73000000 always busy
73C50000-73C51000 /cygdrive/c/Windows/SysWOW64/cryptbase.dll
> 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...
> Corinna
Marco
---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com
--
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-12 16:35 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 [this message]
2018-07-14 17:58 ` Achim Gratz
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=c1aa10ad-e685-f232-6719-5c653f747f83@gmail.com \
--to=marco.atzeri@gmail.com \
--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).