From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Fork issue on W10 WOW
Date: Thu, 12 Jul 2018 12:34:00 -0000 [thread overview]
Message-ID: <CAB8Xom_DX=u0q17ewfRokh_mTcBYMppPZdDLS3UUdaPm5GMV4w@mail.gmail.com> (raw)
In-Reply-To: <fd7e7ce2-84fd-aef3-b54a-0ff76ef8900c@gmail.com>
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
next prev parent reply other threads:[~2018-07-12 10:31 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 [this message]
2018-07-14 12:46 ` Corinna Vinschen
2018-07-14 14:31 ` Marco Atzeri
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='CAB8Xom_DX=u0q17ewfRokh_mTcBYMppPZdDLS3UUdaPm5GMV4w@mail.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).