GNU bug report logs - #29297
linux grep question, please help us to see, thank you

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 29297 in the body.
You can then email your comments to 29297 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Yufuping <fuping.yu <at> huawei.com>
To: "bug-grep <at> gnu.org" <bug-grep <at> gnu.org>
Cc: wumingxin <wumingxin <at> huawei.com>, Huotongyao <huotongyao <at> huawei.com>
Subject: linux grep question, please help us to see, thank you 
Date: Tue, 14 Nov 2017 03:47:22 +0000

[Message part 1 (text/plain, inline)]

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

[cid:image001.png <at> 01D35D3E.3236BD00]

[Message part 2 (text/html, inline)]

[image001.png (image/png, inline)]

Message #10 received at 29297-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Yufuping <fuping.yu <at> huawei.com>
Cc: 29297-done <at> debbugs.gnu.org
Subject: Re: linux grep question, please help us to see, thank you
Date: Tue, 31 Dec 2019 11:56:09 -0800

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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.