emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#29297: closed (linux grep question, please help us to see, thank you


From: GNU bug Tracking System
Subject: bug#29297: closed (linux grep question, please help us to see, thank you )
Date: Tue, 31 Dec 2019 19:57:01 +0000

Your message dated Tue, 31 Dec 2019 11:56:09 -0800
with message-id <address@hidden>
and subject line Re: linux grep question, please help us to see, thank you
has caused the debbugs.gnu.org bug report #29297,
regarding linux grep question, please help us to see, thank you 
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
29297: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29297
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: linux grep question, please help us to see, thank you Date: Tue, 14 Nov 2017 03:47:22 +0000

Hi,

 

when we executed shell, we found that the grep command with wrong write error, and the return value was 2. May I ask where the problem is? And this is a probabilistic problem, Thank you

 


--- End Message ---
--- Begin Message --- Subject: Re: linux grep question, please help us to see, thank you Date: Tue, 31 Dec 2019 11:56:09 -0800 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
Re <https://bugs.gnu.org/29297> dated 2017-11-14:

> the grep command with wrong write error, and the return value was 2. May I 
> ask where the problem is? And this is a probabilistic problem

Grep reports 'write error' if the 'write' system call fails. If 'grep' was
incorrect, it's because the 'write' system call was incorrect. So, as near as I
can see this is not a 'grep' bug and I am closing the bug report.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]