> And only now I've found the messages talking about similar issues after > fruitless Google searches. Same thing happens to me after I buy hardware. > > The problem appears fixed in the latest snapshot of cygwin1.dll.
Indeed it was; the problem happened for at least two other people on the mailing list (including me) and a fix was implemented in the developer snapshot of cygwin1.dll and fixed it for us. Since you are using non-Cygwin programs, you should also be setting the pipe_byte option of the CYGWIN environment variable. Search the mailing list archive for why this is so, but to summarize - there are situations where the non-Cygwin programs may malfunction when processing their standard input streams if this option is not set. (Unfortunately, there is not yet any documentation about this recent issue.) -- 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