From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: grep < fifo fails
Date: Mon, 08 Oct 2018 08:24:00 -0000 [thread overview]
Message-ID: <4749b23a0374bf264ad46a0c7466e73e@smtp-cloud9.xs4all.net> (raw)
In-Reply-To: <8100972155fcccd61852c0c9e48cd11b@smtp-cloud9.xs4all.net>
On Fri, 05 Oct 2018 17:32:16, Houder wrote:
> On Thu, 04 Oct 2018 18:02:03, Houder wrote:
> > On Wed, 03 Oct 2018 20:46:11, Houder wrote:
> > > On Wed, 3 Oct 2018 15:37:14, Ole Tange wrote:
> > > > This works:
> > > >
> > > > $ mkfifo fifo
> > > > $ echo > fifo & grep . fifo
> > > > [1] 10232
> > > > [1]+ Done echo > fifo
> > > >
> > > > But this fails:
> > > >
> > > > $ echo > fifo & grep . < fifo
> > > > [1] 11756
> > > > grep: (standard input): Invalid argument
> > > > [1]+ Done echo > fifo
> > > >
> > > > I see the same behavior on MINGW, but I do not see the same behavior on GNU=
> > > > /Linux.
> >
> > My apologies. Did not read your post as careful as I should have the first time.
> > You are correct: grep is in error here.
>
> Filed this bug at bug-grep@gnu.org; it is filed under number 32943.
>
> - https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32943
>
grep fails on Cygwin because lseek() on Cygwin fails to recognize
that it is applied to a FIFO. As result of that, it returns EINVAL
in errno, where it should return ESPIPE.
Receiving the wrong value in errno forces reset() (in src/grep.c)
to return false, upon which grep fails.
Before v2.27 of grep, a call to S_ISREG(st->st_mode) in reset()
prevented the call of lseek() and made reset() return true.
The call to S_ISREG() has been removed in v2.27 of grep.
The solution would be either to correct Cygwin's executive or to
insert a Cygwin-specific kludge in grep (in reset() ).
Regards,
Henri
--
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
next prev parent reply other threads:[~2018-10-08 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 15:37 Ole Tange
2018-10-03 16:50 ` Marco Atzeri
2018-10-03 18:46 ` Houder
2018-10-04 16:02 ` Houder
2018-10-05 15:32 ` Houder
2018-10-08 8:24 ` Houder [this message]
2018-10-08 15:03 ` Eric Blake
2018-10-10 11:22 ` Corinna Vinschen
2018-10-10 9:53 ` Houder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4749b23a0374bf264ad46a0c7466e73e@smtp-cloud9.xs4all.net \
--to=houder@xs4all.nl \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).