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 starti
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 une
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.
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
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 ref
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:
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
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
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.
>
> U
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
0001000
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 tes
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 exam
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
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 g
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 p
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 t
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.
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 su
18 matches
Mail list logo
