GNU bug report logs - #25180
grep: (standard input): Invalid argument

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#25180: closed (grep: (standard input): Invalid argument)
Date: Mon, 12 Dec 2016 16:41:02 +0000

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

Your message dated Mon, 12 Dec 2016 08:40:09 -0800
with message-id <d912bcbe-0aa2-dffa-d893-31df34e110ae <at> cs.ucla.edu>
and subject line Re: bug#25180: grep: (standard input): Invalid argument
has caused the debbugs.gnu.org bug report #25180,
regarding grep: (standard input): Invalid argument
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
25180: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25180
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Andreas Schwab <schwab <at> suse.de>
To: bug-grep <at> gnu.org
Subject: grep: (standard input): Invalid argument
Date: Mon, 12 Dec 2016 11:10:48 +0100

$ grep ^Sig < /proc/self/status >/dev/null
grep: (standard input): Invalid argument
$ strace -e lseek grep ^Sig < /proc/self/status >/dev/null
lseek(0, 0, SEEK_CUR)                   = 0
lseek(0, 0, SEEK_END)                   = -1 EINVAL (Invalid argument)
grep: (standard input): Invalid argument
+++ exited with 2 +++

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab <at> suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

[Message part 3 (message/rfc822, inline)]

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Andreas Schwab <schwab <at> suse.de>, 25180-done <at> debbugs.gnu.org
Subject: Re: bug#25180: grep: (standard input): Invalid argument
Date: Mon, 12 Dec 2016 08:40:09 -0800

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

Thanks, I didn't know about that lseek glitch with the proc file system. 
I installed the attached patch to the grep master.

The use case seems unusual. Did a user discover this in practice?

[0001-grep-work-around-proc-lseek-glitch.patch (application/x-patch, attachment)]

Previous Next

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