From: Linda Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2
Date: Fri, 04 Dec 2015 16:35:00 -0000 [thread overview]
Message-ID: <5661C0AC.8050209@tlinx.org> (raw)
In-Reply-To: <565DF5E8.5010908@blaeu.com>
Rob van Eijk wrote:
>
> Op 1-12-2015 om 17:40 schreef David Macek:
>> On 1. 12. 2015 15:01, Corinna Vinschen wrote:
>>> 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.
----
Win10 has a 32-bit version?
I thought MS said Win8 was the last version that would
ship in a 32-bit version with their eventual intension to be getting
rid of 32-bit support entirely (for reasons like it supporting
various legacy design constraints that make it harder to manage(control)
as an end-user-platform, for example)?
--
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:[~2015-12-04 16:35 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 [this message]
2015-12-06 14:11 ` Corinna Vinschen
2015-12-01 21:44 ` David Macek
2015-12-02 22:15 ` Corinna Vinschen
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=5661C0AC.8050209@tlinx.org \
--to=cygwin@tlinx.org \
--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).