Hi Paul, I also get Bad File Descriptor errors, though in a quite different situation, see my recent topic "gawk: Bad File Descriptor error with concurrent readonly access to a network file" on Sep 25. There seems to be some issue in some file opening process that occurs with parallel processes and eventually concurrent file access (as in my case). May be the basic problem behind is similar to yours?
Kind regards, Wolfgang > After observing for a week on the system with the fix applied, I did not see > this issue reoccur. > I do however still suspect that it is a bug in cygwin, indeed a race > condition of some sorts, which probably becomes > apparent when starting up a process takes (much) longer than expected. > As said, the guard32.dll is probably scanning the new CreateProcess > candidate. I suspect that there's an timing > assumption in the Cygwin fork code. But as I cannot be sure, I leave it at > that. > > Regards, > Paul
