public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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: Tue, 01 Dec 2015 11:20:00 -0000	[thread overview]
Message-ID: <20151201112037.GU2755@calimero.vinschen.de> (raw)
In-Reply-To: <565D762E.4090109@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]

On Dec  1 19:27, nu774 wrote:
> After upgrading to Windows 10 TH2 (ver 1511, build 10586), any attempt
> to launch a cygwin64 process from 32bit native app (for example,
> C:\windows\syswow64\cmd.exe) *always* results in a fork error.
> 
> To be precise, I can execute 64bit bash.exe from 32bit cmd.exe.
> However, this bash process never succeeds in forking a child (ls or
> something).
> Also, I cannot launch 64bit mintty.exe from 32bit cmd.exe. It always
> fails in a error dialog saying that:
> 
> mintty: could not detach from caller
> Try '--help' for more information.
> 
> When launching from 64bit app, this issue doesn't happen.

I don't have a W10 ver 1511 yet, but even then it's hard to see that
this may be Cygwin's fault.  It worked so far with all versions of
Windows since XP 64, including the pre-1511 W10.

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.


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

  reply	other threads:[~2015-12-01 11:20 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 [this message]
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
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=20151201112037.GU2755@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).