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 wrote: > On Nov 25 19:38, Eli Zaretskii wrote: >> > Date: Wed, 25 Nov 2015 12:37:15 +0100 >> > From: Dominique de Waleffe >> > >> > 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