fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[nu774]

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.

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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[Corinna Vinschen]

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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[nu774]

> 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().


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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[Corinna Vinschen]

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

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


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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[David Macek]

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

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.

-- 
David Macek


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4254 bytes --]

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[Rob van Eijk]

Op 1-12-2015 om 17:40 schreef David Macek:
> 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.
> 

I upgraded today to Windows 10 v1511. I ran into the same problem. I
renamed my cygwin root directory (64 bit) and installed a 32 bit version
of cygwin. The fork problem does not appear on the 32 bit version.

In conclusion, I confirm that the issue appears when running a 32 bit
version from a 64 bit cygwin. It does not appear when running a 32 bit
app from a 32 bit cygwin.

PS: my test applicatin is notepad++ with the nppexec plugin, which I use
to power up the make command in a cygwin shell.

mvg::Rob

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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[Linda Walsh]

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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[Corinna Vinschen]

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

On Dec  4 08:34, Linda Walsh wrote:
> 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)?

I guess given that the ARM version is 32 bit anyway, it didn't hurt
to keep the 32 bit i686 version running as well.


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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[David Macek]

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

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"

-- 
David Macek


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4254 bytes --]

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[Corinna Vinschen]

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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[René Berber]

On 12/2/2015 4:15 PM, Corinna Vinschen wrote:

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

Under 64-bit Cygwin:

$ cat /proc/self/maps
00010000-00020000 rw-s 00000000 0000:0000 0                   [win heap
1 default shared]
00020000-00021000 rw-s 00000000 0000:0000 0
00030000-00044000 r--s 00000000 0000:0000 0
00050000-00247000 ===p 00000000 0000:0000 0                   [stack
(tid 17852)]
00247000-0024A000 rw-g 001F7000 0000:0000 0                   [stack
(tid 17852)]
0024A000-00250000 rw-p 001FA000 0000:0000 0                   [stack
(tid 17852)]
00250000-00254000 r--s 00000000 0000:0000 0
00260000-00261000 r--s 00000000 0000:0000 0
00270000-00272000 rw-p 00000000 0000:0000 0
00280000-0033E000 r--s 00000000 0203:7481 1970324837770000
/cygdrive/c/Windows/System32/locale.nls
00340000-00341000 rw-p 00000000 0000:0000 0                   [win heap
0 default grow]
00341000-00372000 ===p 00001000 0000:0000 0                   [win heap
0 default grow]
00380000-00381000 rw-p 00000000 0000:0000 0                   [win heap
2 grow]
00381000-003B2000 ===p 00001000 0000:0000 0                   [win heap
2 grow]
00430000-0043A000 rw-p 00000000 0000:0000 0                   [win heap
0 default grow]
0043A000-00530000 ===p 0000A000 0000:0000 0                   [win heap
0 default grow]
00530000-0072B000 ===p 00000000 0000:0000 0                   [stack
(tid 18372)]
0072B000-0072E000 rw-g 001FB000 0000:0000 0                   [stack
(tid 18372)]
0072E000-00730000 rw-p 001FE000 0000:0000 0                   [stack
(tid 18372)]
00730000-0092C000 ===p 00000000 0000:0000 0                   [stack
(tid 15144)]
0092C000-0092F000 rw-g 001FC000 0000:0000 0                   [stack
(tid 15144)]
0092F000-00930000 rw-p 001FF000 0000:0000 0                   [stack
(tid 15144)]
00930000-00B2C000 ===p 00000000 0000:0000 0                   [stack
(tid 8304)]
00B2C000-00B2F000 rw-g 001FC000 0000:0000 0                   [stack
(tid 8304)]
00B2F000-00B30000 rw-p 001FF000 0000:0000 0                   [stack
(tid 8304)]
00B30000-00D29000 ===p 00000000 0000:0000 0                   [stack
(tid 6616)]
00D29000-00D2C000 rw-g 001F9000 0000:0000 0                   [stack
(tid 6616)]
00D2C000-00D30000 rw-p 001FC000 0000:0000 0                   [stack
(tid 6616)]
00EA0000-00EA6000 rw-p 00000000 0000:0000 0                   [win heap
2 grow]
00EA6000-00EB0000 ===p 00006000 0000:0000 0                   [win heap
2 grow]
7FFE0000-7FFE1000 r--p 00000000 0000:0000 0
[shared-user-data]
7FFE1000-7FFF0000 ===p 00001000 0000:0000 0
[shared-user-data]
100400000-100401000 r--p 00000000 0203:7481 25051272927416393
/usr/bin/cat.exe
100401000-100409000 r-xp 00001000 0203:7481 25051272927416393
/usr/bin/cat.exe
100409000-10040A000 rw-p 00009000 0203:7481 25051272927416393
/usr/bin/cat.exe
10040A000-10040F000 r--p 0000A000 0203:7481 25051272927416393
/usr/bin/cat.exe
10040F000-100412000 rw-p 0000F000 0203:7481 25051272927416393
/usr/bin/cat.exe
100412000-100413000 r--p 00012000 0203:7481 25051272927416393
/usr/bin/cat.exe
180010000-180020000 rw-s 00000000 0000:0000 0                 [procinfo]
180020000-180029000 rw-s 00000000 0000:0000 0
[cygwin-user-shared]
180030000-18003A000 rw-s 00000000 0000:0000 0
[cygwin-shared]
180040000-180041000 r--p 00000000 0203:7481 17169973579518949
/usr/bin/cygwin1.dll
180041000-1801E7000 r-xp 00001000 0203:7481 17169973579518949
/usr/bin/cygwin1.dll
1801E7000-1801EB000 rwxp 001A7000 0203:7481 17169973579518949
/usr/bin/cygwin1.dll
1801EB000-180212000 rw-p 001AB000 0203:7481 17169973579518949
/usr/bin/cygwin1.dll
180212000-1802BA000 r--p 001D2000 0203:7481 17169973579518949
/usr/bin/cygwin1.dll
1802BA000-180303000 rw-p 0027A000 0203:7481 17169973579518949
/usr/bin/cygwin1.dll
180303000-180313000 r--p 002C3000 0203:7481 17169973579518949
/usr/bin/cygwin1.dll
180313000-180320000 rw-p 002D3000 0203:7481 17169973579518949
/usr/bin/cygwin1.dll
180320000-180321000 r--p 002E0000 0203:7481 17169973579518949
/usr/bin/cygwin1.dll
180321000-180630000 rw-p 002E1000 0203:7481 17169973579518949
/usr/bin/cygwin1.dll
3FF860000-3FF861000 r--p 00000000 0203:7481 10133099161757167
/usr/bin/cygintl-8.dll
3FF861000-3FF867000 r-xp 00001000 0203:7481 10133099161757167
/usr/bin/cygintl-8.dll
3FF867000-3FF868000 rw-p 00007000 0203:7481 10133099161757167
/usr/bin/cygintl-8.dll
3FF868000-3FF86D000 r--p 00008000 0203:7481 10133099161757167
/usr/bin/cygintl-8.dll
3FF86D000-3FF86E000 rw-p 0000D000 0203:7481 10133099161757167
/usr/bin/cygintl-8.dll
3FF86E000-3FF86F000 r--p 0000E000 0203:7481 10133099161757167
/usr/bin/cygintl-8.dll
3FF86F000-3FF871000 rw-p 0000F000 0203:7481 10133099161757167
/usr/bin/cygintl-8.dll
3FF871000-3FF873000 r--p 00011000 0203:7481 10133099161757167
/usr/bin/cygintl-8.dll
3FF880000-3FF881000 r--p 00000000 0203:7481 19703248370073036
/usr/bin/cygiconv-2.dll
3FF881000-3FF899000 r-xp 00001000 0203:7481 19703248370073036
/usr/bin/cygiconv-2.dll
3FF899000-3FF89A000 rw-p 00019000 0203:7481 19703248370073036
/usr/bin/cygiconv-2.dll
3FF89A000-3FF97F000 r--p 0001A000 0203:7481 19703248370073036
/usr/bin/cygiconv-2.dll
3FF97F000-3FF980000 rw-p 000FF000 0203:7481 19703248370073036
/usr/bin/cygiconv-2.dll
3FF980000-3FF981000 r--p 00100000 0203:7481 19703248370073036
/usr/bin/cygiconv-2.dll
3FF981000-3FF983000 rw-p 00101000 0203:7481 19703248370073036
/usr/bin/cygiconv-2.dll
3FF983000-3FF985000 r--p 00103000 0203:7481 19703248370073036
/usr/bin/cygiconv-2.dll
600000000-600080000 rw-p 00000000 0000:0000 0                 [heap]
600080000-620000000 ===p 00080000 0000:0000 0                 [heap]
7FF5FFED0000-7FF5FFED5000 r--s 00000000 0000:0000 0
7FF5FFED5000-7FF5FFFD0000 ===s 00005000 0000:0000 0
7FF5FFFD0000-7FF5FFFF3000 r--s 00000000 0000:0000 0
7FF5FFFF4000-7FF5FFFF6000 rw-p 00000000 0000:0000 0           [teb (tid
6616)]
7FF5FFFF6000-7FF5FFFF8000 rw-p 00000000 0000:0000 0           [teb (tid
8304)]
7FF5FFFF8000-7FF5FFFF9000 rw-p 00000000 0000:0000 0           [peb]
7FF5FFFF9000-7FF5FFFFB000 rw-p 00000000 0000:0000 0           [teb (tid
15144)]
7FF5FFFFB000-7FF5FFFFD000 rw-p 00000000 0000:0000 0           [teb (tid
18372)]
7FF5FFFFD000-7FF5FFFFF000 rw-p 00000000 0000:0000 0           [teb (tid
17852)]
7FFE7F4A0000-7FFE7F4A1000 r--p 00000000 0203:7481 1970324837771067
/cygdrive/c/Windows/System32/KernelBase.dll
7FFE7F4A1000-7FFE7F56A000 r-xp 00001000 0203:7481 1970324837771067
/cygdrive/c/Windows/System32/KernelBase.dll
7FFE7F56A000-7FFE7F655000 r--p 000CA000 0203:7481 1970324837771067
/cygdrive/c/Windows/System32/KernelBase.dll
7FFE7F655000-7FFE7F65A000 rw-p 001B5000 0203:7481 1970324837771067
/cygdrive/c/Windows/System32/KernelBase.dll
7FFE7F65A000-7FFE7F67D000 r--p 001BA000 0203:7481 1970324837771067
/cygdrive/c/Windows/System32/KernelBase.dll
7FFE7F900000-7FFE7F901000 r--p 00000000 0203:7481 1970324837771066
/cygdrive/c/Windows/System32/kernel32.dll
7FFE7F901000-7FFE7F974000 r-xp 00001000 0203:7481 1970324837771066
/cygdrive/c/Windows/System32/kernel32.dll
7FFE7F974000-7FFE7F9A3000 r--p 00074000 0203:7481 1970324837771066
/cygdrive/c/Windows/System32/kernel32.dll
7FFE7F9A3000-7FFE7F9A4000 rw-p 000A3000 0203:7481 1970324837771066
/cygdrive/c/Windows/System32/kernel32.dll
7FFE7F9A4000-7FFE7F9AD000 r--p 000A4000 0203:7481 1970324837771066
/cygdrive/c/Windows/System32/kernel32.dll
7FFE7FC60000-7FFE7FC61000 r--p 00000000 0203:7481 3096224744698258
/cygdrive/c/Windows/System32/rpcrt4.dll
7FFE7FC61000-7FFE7FD44000 r-xp 00001000 0203:7481 3096224744698258
/cygdrive/c/Windows/System32/rpcrt4.dll
7FFE7FD44000-7FFE7FD6F000 r--p 000E4000 0203:7481 3096224744698258
/cygdrive/c/Windows/System32/rpcrt4.dll
7FFE7FD6F000-7FFE7FD71000 rw-p 0010F000 0203:7481 3096224744698258
/cygdrive/c/Windows/System32/rpcrt4.dll
7FFE7FD71000-7FFE7FD86000 r--p 00111000 0203:7481 3096224744698258
/cygdrive/c/Windows/System32/rpcrt4.dll
7FFE80490000-7FFE80491000 r--p 00000000 0203:7481 1970324837771393
/cygdrive/c/Windows/System32/sechost.dll
7FFE80491000-7FFE804C4000 r-xp 00001000 0203:7481 1970324837771393
/cygdrive/c/Windows/System32/sechost.dll
7FFE804C4000-7FFE804E2000 r--p 00034000 0203:7481 1970324837771393
/cygdrive/c/Windows/System32/sechost.dll
7FFE804E2000-7FFE804E5000 rw-p 00052000 0203:7481 1970324837771393
/cygdrive/c/Windows/System32/sechost.dll
7FFE804E5000-7FFE804EB000 r--p 00055000 0203:7481 1970324837771393
/cygdrive/c/Windows/System32/sechost.dll
7FFE804F0000-7FFE804F1000 r--p 00000000 0203:7481 1970324837771188
/cygdrive/c/Windows/System32/msvcrt.dll
7FFE804F1000-7FFE80565000 r-xp 00001000 0203:7481 1970324837771188
/cygdrive/c/Windows/System32/msvcrt.dll
7FFE80565000-7FFE8057E000 r--p 00075000 0203:7481 1970324837771188
/cygdrive/c/Windows/System32/msvcrt.dll
7FFE8057E000-7FFE80586000 rw-p 0008E000 0203:7481 1970324837771188
/cygdrive/c/Windows/System32/msvcrt.dll
7FFE80586000-7FFE8058D000 r--p 00096000 0203:7481 1970324837771188
/cygdrive/c/Windows/System32/msvcrt.dll
7FFE82040000-7FFE82041000 r--p 00000000 0203:7481 1970324837770328
/cygdrive/c/Windows/System32/advapi32.dll
7FFE82041000-7FFE820A4000 r-xp 00001000 0203:7481 1970324837770328
/cygdrive/c/Windows/System32/advapi32.dll
7FFE820A4000-7FFE820D8000 r--p 00064000 0203:7481 1970324837770328
/cygdrive/c/Windows/System32/advapi32.dll
7FFE820D8000-7FFE820DD000 rw-p 00098000 0203:7481 1970324837770328
/cygdrive/c/Windows/System32/advapi32.dll
7FFE820DD000-7FFE820E6000 r--p 0009D000 0203:7481 1970324837770328
/cygdrive/c/Windows/System32/advapi32.dll
7FFE820F0000-7FFE820F1000 r--p 00000000 0203:7481 6755399441936788
/cygdrive/c/Windows/System32/ntdll.dll
7FFE820F1000-7FFE821ED000 r-xp 00001000 0203:7481 6755399441936788
/cygdrive/c/Windows/System32/ntdll.dll
7FFE821ED000-7FFE8222F000 r--p 000FD000 0203:7481 6755399441936788
/cygdrive/c/Windows/System32/ntdll.dll
7FFE8222F000-7FFE82238000 rw-p 0013F000 0203:7481 6755399441936788
/cygdrive/c/Windows/System32/ntdll.dll
7FFE82238000-7FFE822B1000 r--p 00148000 0203:7481 6755399441936788
/cygdrive/c/Windows/System32/ntdll.dll
7FFFFFFE0000-7FFFFFFF0000 ===p 00000000 0000:0000 0

$ uname -a
CYGWIN_NT-10.0 T7400 2.3.1(0.291/5/3) 2015-11-14 12:44 x86_64 Cygwin

I don't know were you can see the specific Windows version, but AFAIK it
hasn't been updated recently (the System Info only shows "Windows 10
Pro", 64-bit).
-- 
René Berber


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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[Corinna Vinschen]

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

On Dec  2 16:43, René Berber wrote:
> On 12/2/2015 4:15 PM, Corinna Vinschen wrote:
> 
> > 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.
> 
> Under 64-bit Cygwin:
> 
> [...]

Thanks a lot!

Does anybody have the same info for 32 bit W10 updated to 1511?
I have the exact opposite info available right now :}

> $ uname -a
> CYGWIN_NT-10.0 T7400 2.3.1(0.291/5/3) 2015-11-14 12:44 x86_64 Cygwin
> 
> I don't know were you can see the specific Windows version, but AFAIK it
> hasn't been updated recently (the System Info only shows "Windows 10
> Pro", 64-bit).

That's oh so funny:  The good old system info doesn't show this anymore.
But you can look into the new-style  "Settings" -> System -> About.


Thanks again,
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 --]

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[David Macek]

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

On 3. 12. 2015 0:00, Corinna Vinschen wrote:
> On Dec  2 16:43, René Berber wrote:
>> I don't know were you can see the specific Windows version, but AFAIK it
>> hasn't been updated recently (the System Info only shows "Windows 10
>> Pro", 64-bit).
> 
> That's oh so funny:  The good old system info doesn't show this anymore.
> But you can look into the new-style  "Settings" -> System -> About.

I've always used the trusty `winver` for version info.

-- 
David Macek


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4254 bytes --]

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[René Berber]

On 12/3/2015 2:13 AM, David Macek wrote:

> I've always used the trusty `winver` for version info.

Thanks.

But I don't know what to make of this: Version 10.0 (build 10240),
perhaps the "1511" is the last 4 digits.
-- 
René Berber



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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[René Berber]

On 12/3/2015 12:56 PM, René Berber wrote:

> But I don't know what to make of this: Version 10.0 (build 10240),
> perhaps the "1511" is the last 4 digits.

Never-mind, Windows update just installed "version 1511, 10586".
-- 
René Berber




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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[Corinna Vinschen]

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

On Dec  3 00:00, Corinna Vinschen wrote:
> On Dec  2 16:43, René Berber wrote:
> > On 12/2/2015 4:15 PM, Corinna Vinschen wrote:
> > 
> > > 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.
> > 
> > Under 64-bit Cygwin:
> > 
> > [...]
> 
> Thanks a lot!
> 
> Does anybody have the same info for 32 bit W10 updated to 1511?
> I have the exact opposite info available right now :}

Never mind this request, I now have a 32 bit W10 1511 myself.


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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[Thomas Wolff]

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

Re: fork issue when lauching cygwin64 process from 32bit native app on Windows 10 TH2

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1101 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 created a workaround for this issue and uploaded new developer
snapshots to https://cygwin.com/snapshots, as well as a new Cygwin
test release 2.4.0-0.7 with this change
(https://cygwin.com/ml/cygwin-announce/2015-12/msg00001.html)

Please give any of them a try.


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