public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2
Date: Thu, 03 Dec 2015 19:09:00 -0000	[thread overview]
Message-ID: <56609361.6070609@towo.net> (raw)
In-Reply-To: <20151201140105.GW2755@calimero.vinschen.de>

Am 01.12.2015 um 15:01 schrieb Corinna Vinschen:
>> ...
> 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 :(
For reference, this has also been reported on 
https://github.com/mintty/mintty/issues/493
Thomas

--
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

  parent reply	other threads:[~2015-12-03 19:09 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
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 [this message]
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=56609361.6070609@towo.net \
    --to=towo@towo.net \
    --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).