On Wed, Mar 09, 2011 at 07:24:11PM +0100, Robert Wruck wrote: >On Mon, Mar 07, 2011 at 11:39:51AM +0100, Corinna Vinschen wrote >>Hang on, you are saying that a *blocking* write(2) to a pipe returns >>with EAGAIN? Are you sure? It would be quite a surprise if git would >>actually do that. EAGAIN is only an expected error for non-blocking >>I/O, so applications which use blocking I/O usually only test for >>EINTR. > > >What I found out: > >In fhandler.cc, write_overlapped, there is the call to WriteFile: > > bool res = WriteFile (get_output_handle (), ptr, len, &nbytes, > get_overlapped ()); > >Surprisingly, this returns FALSE / nbytes = 0 / GetLastError = >ERROR_INVALID_HANDLE on WinXP if the number of bytes exceeds some >maximum and the handle refers to a pipe.
Knock, knock. Is this thing on? http://cygwin.com/ml/cygwin/2011-03/msg00226.html http://cygwin.com/ml/cygwin/2011-03/msg00280.html -- 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
