Re: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

Re: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

[Eli Zaretskii]

> Date: Wed, 25 Nov 2015 12:37:15 +0100
> From: Dominique de Waleffe <ddewaleffe@gmail.com>
> 
> bash: cannot set terminal process group (-1): Inappropriate ioctl for device
> bash: no job control in this shell
> 1 [main] bash 9588 c:\s\cygwin64\bin\bash.exe: *** fatal error in forked
> process - fork: can't reserve memory for parent stack 0x600000 - 0x800000,
> (child has 0x400000 - 0x600000), Win32 error 487
> 1115 [main] bash 9588 cygwin_exception::open_stackdumpfile: Dumping stack trace
> to bash.exe.stackdump
> 1 [main] bash 16396 fork: child -1 - forked process 9588 died unexpectedly,
> retry 0, exit code 0x100, errno 11
> bash: fork: retry: No child processes
> 1018684 [main] bash 14236 c:\s\cygwin64\bin\bash.exe: *** fatal error in forked
> process - fork: can't reserve memory for parent stack 0x600000 - 0x800000,
> (child has 0x400000 - 0x600000), Win32 error 487
> 1019772 [main] bash 14236 cygwin_exception::open_stackdumpfile: Dumping stack
> trace to bash.exe.stackdump
> 1157135 [main] bash 16396 fork: child -1 - forked process 14236 died
> unexpectedly, retry 0, exit code 0x100, errno 11

These are Cygwin errors, which I hope Cygwin folks will be able to
interpret.  Perhaps the stack dump trace produced by this will help
them even more, so I suggest to post its contents.

--
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: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

[Dominique de Waleffe]

Before upgrading another machine (still on win7/64), I updated
cygwin64 on it and pulled fsfemacs 24.5 (the existing binary on gnu's
site) on it...

Did the same test there and on win7 it works. Could this be a Windows
10 related issue?

D.
PS: I'll stop cc'ing the emacs list after this message as I also think
it is more likely a cygwin issue.
############################
# Dominique de Waleffe
# ddewaleffe -at- gmail -dot- com
############################


On Wed, Nov 25, 2015 at 6:38 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 25 Nov 2015 12:37:15 +0100
>> From: Dominique de Waleffe <ddewaleffe@gmail.com>
>>
>> bash: cannot set terminal process group (-1): Inappropriate ioctl for device
>> bash: no job control in this shell
>> 1 [main] bash 9588 c:\s\cygwin64\bin\bash.exe: *** fatal error in forked
>> process - fork: can't reserve memory for parent stack 0x600000 - 0x800000,
>> (child has 0x400000 - 0x600000), Win32 error 487
>> 1115 [main] bash 9588 cygwin_exception::open_stackdumpfile: Dumping stack trace
>> to bash.exe.stackdump
>> 1 [main] bash 16396 fork: child -1 - forked process 9588 died unexpectedly,
>> retry 0, exit code 0x100, errno 11
>> bash: fork: retry: No child processes
>> 1018684 [main] bash 14236 c:\s\cygwin64\bin\bash.exe: *** fatal error in forked
>> process - fork: can't reserve memory for parent stack 0x600000 - 0x800000,
>> (child has 0x400000 - 0x600000), Win32 error 487
>> 1019772 [main] bash 14236 cygwin_exception::open_stackdumpfile: Dumping stack
>> trace to bash.exe.stackdump
>> 1157135 [main] bash 16396 fork: child -1 - forked process 14236 died
>> unexpectedly, retry 0, exit code 0x100, errno 11
>
> These are Cygwin errors, which I hope Cygwin folks will be able to
> interpret.  Perhaps the stack dump trace produced by this will help
> them even more, so I suggest to post its contents.

--
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: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

[Corinna Vinschen]

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

On Nov 25 19:38, Eli Zaretskii wrote:
> > Date: Wed, 25 Nov 2015 12:37:15 +0100
> > From: Dominique de Waleffe <ddewaleffe@gmail.com>
> > 
> > bash: cannot set terminal process group (-1): Inappropriate ioctl for device
> > bash: no job control in this shell
> > 1 [main] bash 9588 c:\s\cygwin64\bin\bash.exe: *** fatal error in forked
> > process - fork: can't reserve memory for parent stack 0x600000 - 0x800000,
> > (child has 0x400000 - 0x600000), Win32 error 487
> > 1115 [main] bash 9588 cygwin_exception::open_stackdumpfile: Dumping stack trace
> > to bash.exe.stackdump
> > 1 [main] bash 16396 fork: child -1 - forked process 9588 died unexpectedly,
> > retry 0, exit code 0x100, errno 11
> > bash: fork: retry: No child processes
> > 1018684 [main] bash 14236 c:\s\cygwin64\bin\bash.exe: *** fatal error in forked
> > process - fork: can't reserve memory for parent stack 0x600000 - 0x800000,
> > (child has 0x400000 - 0x600000), Win32 error 487
> > 1019772 [main] bash 14236 cygwin_exception::open_stackdumpfile: Dumping stack
> > trace to bash.exe.stackdump
> > 1157135 [main] bash 16396 fork: child -1 - forked process 14236 died
> > unexpectedly, retry 0, exit code 0x100, errno 11

https://cygwin.com/faq/faq.html#faq.using.fixing-fork-failures

> These are Cygwin errors, which I hope Cygwin folks will be able to
> interpret.  Perhaps the stack dump trace produced by this will help
> them even more, so I suggest to post its contents.

So it looks like this is either a BLODA(*) problem, or rebasing the
entire distro is necessary(**).


Corinna


(*)  https://cygwin.com/faq/faq.html#faq.using.bloda
(**) https://cygwin.com/ml/cygwin-announce/2015-02/msg00014.html

-- 
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: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

[Dominique de Waleffe]

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

Corinna,
Thanks for the pointer.

I have checked the BLODA list. The only thing I have is windows
defender (part of the os:-(
It can be disabled via  group policy. (but I am not tempted to do that
for long term)
I did that but same issue...

I have rebased the whole cygwin as suggested also.
That did not fix the problem either.

I attached the bash stack trace in case it may help.

If you have any idea as to what I could do to help debug this... I'll
be happy to help.

Meanwhile, I'll make a VM with a fresh install of Win10 (v1511 x64)
and just Emacs + cygwin and see whether there is something fishy about
my current setup after the upgrades it went through...

D.

############################
# Dominique de Waleffe
# ddewaleffe -at- gmail -dot- com
############################


On Thu, Nov 26, 2015 at 2:51 PM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> On Nov 25 19:38, Eli Zaretskii wrote:
>> > Date: Wed, 25 Nov 2015 12:37:15 +0100
>> > From: Dominique de Waleffe <ddewaleffe@gmail.com>
>> >
>> > bash: cannot set terminal process group (-1): Inappropriate ioctl for device
>> > bash: no job control in this shell
>> > 1 [main] bash 9588 c:\s\cygwin64\bin\bash.exe: *** fatal error in forked
>> > process - fork: can't reserve memory for parent stack 0x600000 - 0x800000,
>> > (child has 0x400000 - 0x600000), Win32 error 487
>> > 1115 [main] bash 9588 cygwin_exception::open_stackdumpfile: Dumping stack trace
>> > to bash.exe.stackdump
>> > 1 [main] bash 16396 fork: child -1 - forked process 9588 died unexpectedly,
>> > retry 0, exit code 0x100, errno 11
>> > bash: fork: retry: No child processes
>> > 1018684 [main] bash 14236 c:\s\cygwin64\bin\bash.exe: *** fatal error in forked
>> > process - fork: can't reserve memory for parent stack 0x600000 - 0x800000,
>> > (child has 0x400000 - 0x600000), Win32 error 487
>> > 1019772 [main] bash 14236 cygwin_exception::open_stackdumpfile: Dumping stack
>> > trace to bash.exe.stackdump
>> > 1157135 [main] bash 16396 fork: child -1 - forked process 14236 died
>> > unexpectedly, retry 0, exit code 0x100, errno 11
>
> https://cygwin.com/faq/faq.html#faq.using.fixing-fork-failures
>
>> These are Cygwin errors, which I hope Cygwin folks will be able to
>> interpret.  Perhaps the stack dump trace produced by this will help
>> them even more, so I suggest to post its contents.
>
> So it looks like this is either a BLODA(*) problem, or rebasing the
> entire distro is necessary(**).
>
>
> Corinna
>
>
> (*)  https://cygwin.com/faq/faq.html#faq.using.bloda
> (**) https://cygwin.com/ml/cygwin-announce/2015-02/msg00014.html
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 cygwin AT cygwin DOT com
> Red Hat

[-- Attachment #2: bash.exe.stackdump --]
[-- Type: application/octet-stream, Size: 777 bytes --]

Stack trace:
Frame        Function    Args
00000000000  00180071F8E (00180212FDC, 00180212E86, 00000400000, 000005FEE10)
00000000000  00180046E22 (000005FFE78, 00000000000, 00000000000, 00000002000)
00000000000  00180046E62 (00000600000, 00000800000, 00000400000, 00000600000)
00000000000  00180047161 (00000000000, 00100401000, 00000284000, 00000000000)
00000000000  001800471AE (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00100472DD1 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00100401010 (00000000000, 00000000000, 00000000000, 00100401000)
00000000000  7FF8E0218102 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  7FF8E12FC264 (00000000000, 00000000000, 00000000000, 00000000000)
End of stack trace

[-- Attachment #3: Type: text/plain, Size: 218 bytes --]

--
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: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

[Achim Gratz]

Dominique de Waleffe writes:
> Meanwhile, I'll make a VM with a fresh install of Win10 (v1511 x64)
> and just Emacs + cygwin and see whether there is something fishy about
> my current setup after the upgrades it went through...

Is there any reason why you don't use the Emacs that comes with Cygwin?
Rebasing Cygwin won't help a bit if some of the GNUwin or MinGW
(depending on the build) librraies that Emacs is compiled with collide
in that same address space.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

--
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: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

[Dominique de Waleffe]

There never was any reason to do as I have so far always been able to
run a version of Emacs compiled without cygwin without any blocking
issue but still running cygwin tools under emacs (and that has been a
case for a very long time!).  I have no religious opinion on this but
I don't see why I should add a dependency that, in "principle" should
not be needed.

The previous build of Emacs on the gnu site was already build with
mingw and afaik it works. It is just that the current combination does
not, in my case. I have no clue as to which version of mingw is
involved in those two emacs builds. But maybe you're onto something
there... Do you have any suggestion as how to validate your
hypothesis?

My goal is not to complain and just have a quick work around, I'd
rather report the issue and if possible help in resolving the issue...
I see that my download has finished... I'll setup this vm and try what
I can with it....

Regards,

D.



############################
# Dominique de Waleffe
# ddewaleffe -at- gmail -dot- com
############################


On Thu, Nov 26, 2015 at 7:00 PM, Achim Gratz <Stromeko@nexgo.de> wrote:
> Dominique de Waleffe writes:
>> Meanwhile, I'll make a VM with a fresh install of Win10 (v1511 x64)
>> and just Emacs + cygwin and see whether there is something fishy about
>> my current setup after the upgrades it went through...
>
> Is there any reason why you don't use the Emacs that comes with Cygwin?
> Rebasing Cygwin won't help a bit if some of the GNUwin or MinGW
> (depending on the build) librraies that Emacs is compiled with collide
> in that same address space.
>
>
> Regards,
> Achim.
> --
> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>
> Samples for the Waldorf Blofeld:
> http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
>
> --
> 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
>

--
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: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

[Dominique de Waleffe]

So... started my homework... Got fresh w10 vm, put cygwin64 and both
versions of emacs 24.4 and 24.5 from fsf ftp onto it....

And trying to start bash as shell fails under both  versions!

=> I was mistaken in the origin of my instance of 24.4 (it must have
come from another source, and I do not remember which)....
     It says: GNU Emacs 24.4.1 (x86_64-w64-mingw32)  of 2014-10-21 on KAEL

=> both versions from fsf ftp appear to be compiled using mingw
     GNU Emacs 24.5.1 (i686-pc-mingw32) of 2015-04-11 on LEG570
     GNU Emacs 24.4.1 (i686-pc-mingw32) of 2014-10-24 on LEG570

So the difference seems to be in the difference of mingw compilation mode.

That's as far as I got tonight. Maybe someone has knowledge to share
about the cause and what to do about this?

Regards,

D.





############################
# Dominique de Waleffe
# ddewaleffe -at- gmail -dot- com
############################


On Thu, Nov 26, 2015 at 8:10 PM, Dominique de Waleffe
<ddewaleffe@gmail.com> wrote:
> There never was any reason to do as I have so far always been able to
> run a version of Emacs compiled without cygwin without any blocking
> issue but still running cygwin tools under emacs (and that has been a
> case for a very long time!).  I have no religious opinion on this but
> I don't see why I should add a dependency that, in "principle" should
> not be needed.
>
> The previous build of Emacs on the gnu site was already build with
> mingw and afaik it works. It is just that the current combination does
> not, in my case. I have no clue as to which version of mingw is
> involved in those two emacs builds. But maybe you're onto something
> there... Do you have any suggestion as how to validate your
> hypothesis?
>
> My goal is not to complain and just have a quick work around, I'd
> rather report the issue and if possible help in resolving the issue...
> I see that my download has finished... I'll setup this vm and try what
> I can with it....
>
> Regards,
>
> D.
>
>
>
> ############################
> # Dominique de Waleffe
> # ddewaleffe -at- gmail -dot- com
> ############################
>
>
> On Thu, Nov 26, 2015 at 7:00 PM, Achim Gratz <Stromeko@nexgo.de> wrote:
>> Dominique de Waleffe writes:
>>> Meanwhile, I'll make a VM with a fresh install of Win10 (v1511 x64)
>>> and just Emacs + cygwin and see whether there is something fishy about
>>> my current setup after the upgrades it went through...
>>
>> Is there any reason why you don't use the Emacs that comes with Cygwin?
>> Rebasing Cygwin won't help a bit if some of the GNUwin or MinGW
>> (depending on the build) librraies that Emacs is compiled with collide
>> in that same address space.
>>
>>
>> Regards,
>> Achim.
>> --
>> +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
>>
>> Samples for the Waldorf Blofeld:
>> http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
>>
>> --
>> 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
>>

--
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: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

[Eli Zaretskii]

> Date: Thu, 26 Nov 2015 22:20:18 +0100
> From: Dominique de Waleffe <ddewaleffe@gmail.com>
> 
> So... started my homework... Got fresh w10 vm, put cygwin64 and both
> versions of emacs 24.4 and 24.5 from fsf ftp onto it....
> 
> And trying to start bash as shell fails under both  versions!
> 
> => I was mistaken in the origin of my instance of 24.4 (it must have
> come from another source, and I do not remember which)....
>      It says: GNU Emacs 24.4.1 (x86_64-w64-mingw32)  of 2014-10-21 on KAEL
> 
> => both versions from fsf ftp appear to be compiled using mingw
>      GNU Emacs 24.5.1 (i686-pc-mingw32) of 2015-04-11 on LEG570
>      GNU Emacs 24.4.1 (i686-pc-mingw32) of 2014-10-24 on LEG570
> 
> So the difference seems to be in the difference of mingw compilation mode.
> 
> That's as far as I got tonight. Maybe someone has knowledge to share
> about the cause and what to do about this?

I'd say this is somehow related to 64-bit Cygwin programs being run by
32-bit native Windows programs.  The version which works for you is a
64-bit executable, those that don't are 32-bit.

Maybe there are compatibility issues vis-à-vis 64-bit Cygwin.

--
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: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

[Dominique de Waleffe]

Thanks, I'll look in that direction...

Next question is where can I find an official Emacs 64-bit build?

Went to the FAQ, read it at
(https://www.gnu.org/software/emacs/manual/html_node/efaq-w32/Downloading.html)
it says it should be on the ftp site  and there would be both a 32 and
64 bit versions but apparently there is only one of them, the 32
bit.... which I mistakenly took for the 64 bit. This probably
explains....

Google a bit further, and it appears that some guy/team publishes a 64
bit build on sourceforge.
http://sourceforge.net/projects/emacsbinw64/ but it has nothing
official and it evolves along with the most recent sources apparently.

Just  now found
https://lists.gnu.org/archive/html/bug-gnu-emacs/2015-06/msg00729.html....
discussing this issue :-)

BTW, I'll also give a try at the cygwin emacs build.

I'll also look at building Emacs from source for x64....

Conclusion:
- I now have a version (25.xx) that works with cygwin64 bash....
- FAQ still a somewhat misleading
- I'll have a look at building  Emacs from source.... and see how to
share the results.

Thanks anyway to all.

D.



############################
# Dominique de Waleffe
# ddewaleffe -at- gmail -dot- com
############################


On Fri, Nov 27, 2015 at 8:31 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Thu, 26 Nov 2015 22:20:18 +0100
>> From: Dominique de Waleffe <ddewaleffe@gmail.com>
>>
>> So... started my homework... Got fresh w10 vm, put cygwin64 and both
>> versions of emacs 24.4 and 24.5 from fsf ftp onto it....
>>
>> And trying to start bash as shell fails under both  versions!
>>
>> => I was mistaken in the origin of my instance of 24.4 (it must have
>> come from another source, and I do not remember which)....
>>      It says: GNU Emacs 24.4.1 (x86_64-w64-mingw32)  of 2014-10-21 on KAEL
>>
>> => both versions from fsf ftp appear to be compiled using mingw
>>      GNU Emacs 24.5.1 (i686-pc-mingw32) of 2015-04-11 on LEG570
>>      GNU Emacs 24.4.1 (i686-pc-mingw32) of 2014-10-24 on LEG570
>>
>> So the difference seems to be in the difference of mingw compilation mode.
>>
>> That's as far as I got tonight. Maybe someone has knowledge to share
>> about the cause and what to do about this?
>
> I'd say this is somehow related to 64-bit Cygwin programs being run by
> 32-bit native Windows programs.  The version which works for you is a
> 64-bit executable, those that don't are 32-bit.
>
> Maybe there are compatibility issues vis-à-vis 64-bit Cygwin.

--
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: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

[Eli Zaretskii]

> Date: Fri, 27 Nov 2015 10:00:11 +0100
> From: Dominique de Waleffe <ddewaleffe@gmail.com>
> Cc: cygwin@cygwin.com, help-emacs-windows@gnu.org
> 
> Next question is where can I find an official Emacs 64-bit build?

There is none.

--
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: [h-e-w] cygwin-64 2.3.1. bash fails when running under FSF emacs 24.5

[Ken Brown]

On 11/27/2015 2:31 AM, Eli Zaretskii wrote:
>> Date: Thu, 26 Nov 2015 22:20:18 +0100
>> From: Dominique de Waleffe <ddewaleffe@gmail.com>
>>
>> So... started my homework... Got fresh w10 vm, put cygwin64 and both
>> versions of emacs 24.4 and 24.5 from fsf ftp onto it....
>>
>> And trying to start bash as shell fails under both  versions!
>>
>> => I was mistaken in the origin of my instance of 24.4 (it must have
>> come from another source, and I do not remember which)....
>>       It says: GNU Emacs 24.4.1 (x86_64-w64-mingw32)  of 2014-10-21 on KAEL
>>
>> => both versions from fsf ftp appear to be compiled using mingw
>>       GNU Emacs 24.5.1 (i686-pc-mingw32) of 2015-04-11 on LEG570
>>       GNU Emacs 24.4.1 (i686-pc-mingw32) of 2014-10-24 on LEG570
>>
>> So the difference seems to be in the difference of mingw compilation mode.
>>
>> That's as far as I got tonight. Maybe someone has knowledge to share
>> about the cause and what to do about this?
>
> I'd say this is somehow related to 64-bit Cygwin programs being run by
> 32-bit native Windows programs.  The version which works for you is a
> 64-bit executable, those that don't are 32-bit.

Just to follow up on this for the sake of the archives, Eli is correct 
(no surprise).  The problem seems to be a result of recent changes to 
Windows 10, and Corinna is working on a fix.  See

   https://www.cygwin.com/ml/cygwin/2015-12/msg00003.html

Ken

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