From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2
Date: Wed, 02 Dec 2015 22:15:00 -0000 [thread overview]
Message-ID: <20151202221521.GH18447@calimero.vinschen.de> (raw)
In-Reply-To: <565E14BA.60204@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]
On Dec 1 22:44, David Macek wrote:
> On 1. 12. 2015 18:40, David Macek wrote:
> > On 1. 12. 2015 15:01, Corinna Vinschen wrote:
> >> On Dec 1 21:07, nu774 wrote:
> >>>> There must be a bug in the new CMD somewhere. But, anyway, I'll look
> >>>> into it when I finally managed to update my W10 test machine.
> >>>
> >>> No, cmd.exe is just an example. Any 32bit process can be an trigger.
> >>> I guess something has changed in TH2 kernel regarding process memory
> >>> management or something that interferes cygwin's fork().
> >>
> >> If that only happens w/ 64 bit Cygwin started from a 32 bit parent, then
> >> there's some foul-up in the WOW64 layer in terms of starting 64 bit
> >> processes, perhaps. Sigh, it's a rather unexpected change after it
> >> worked fine for so long :(
> >
> > Yup. I can confirm.
>
> Just for the record, we did some debugging over IRC and it seems it's an issue with WOW64 where the stack in the first 64-bit process is offset for some reason.
>
> Citing Corinna: "I wonder if we have to resurrect the old wow64_respawn_process function for this border case"
Along these lines, is anybody here still running a 64 bit Windows 10
which has *NOT* been updated to 1511? If so, I just need the output
of a call to `cat /proc/self/maps' once for comparison.
Thanks in advance,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-12-02 22:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 10:28 nu774
2015-12-01 11:20 ` Corinna Vinschen
2015-12-01 12:07 ` nu774
2015-12-01 14:01 ` Corinna Vinschen
2015-12-01 17:40 ` David Macek
2015-12-01 19:33 ` Rob van Eijk
2015-12-04 16:35 ` Linda Walsh
2015-12-06 14:11 ` Corinna Vinschen
2015-12-01 21:44 ` David Macek
2015-12-02 22:15 ` Corinna Vinschen [this message]
2015-12-02 22:44 ` René Berber
2015-12-02 23:00 ` Corinna Vinschen
2015-12-03 8:13 ` David Macek
2015-12-03 18:58 ` René Berber
2015-12-03 19:09 ` René Berber
2015-12-03 10:43 ` Corinna Vinschen
2015-12-03 19:09 ` Thomas Wolff
2015-12-03 22:52 ` Corinna Vinschen
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=20151202221521.GH18447@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).