Spurious 'grep: writing output' in Cygwin 1.7.5-1 in certain cases
Christopher Faylor
cgf-use-the-mailinglist-please@cygwin.com
Tue Apr 20 00:50:00 GMT 2010
On Mon, Apr 19, 2010 at 05:37:55PM -0600, Eric Blake wrote:
>[adding bug-grep]
>
>On 04/19/2010 03:19 PM, Matthew Kidd wrote:
>> We are seeing grep emit 'grep: writing output' multiple times in
>> certain cases where the output of grep is piped to another program.
>> Specifically, we see it in the following cases:
>>
>> grep thisandthat foo.txt | head
>> grep thisandthat foo.txt | less
>
>Expected, if you are blocking SIGPIPE, although it might be improved a
>bit. Grep is telling you that it encountered a write failure due to
>EPIPE, and is thus about to exit with non-zero status. Did you paste
>the full error message? On Linux, I see:
>
>grep: writing output: Broken pipe
Apparently grep isn't seeing an actual EPIPE here for some reason. I
will look into why that is the case.
cgf
--
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
More information about the Cygwin
mailing list