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
