[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange behaviour on 'read' from a pipe
From: |
Lluís Batlle i Rossell |
Subject: |
Re: Strange behaviour on 'read' from a pipe |
Date: |
Sun, 1 Apr 2012 19:02:35 +0200 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Sun, Apr 01, 2012 at 11:06:22AM -0400, Chet Ramey wrote:
> On 4/1/12 5:53 AM, Andreas Schwab wrote:
>
> >> It looks like a simple race condition. I suspect that the scheduler
> >> arranges things so that the child process ends up exiting between the
> >> open and the read, but I don't have any real evidence to back it up.
> >
> > Note that the opening of the pipe as part of the redirection in the
> > parent blocks until there is a writer, ie. until the child opens the
> > pipe. Can this open call return EINTR?
>
> open() is supposed to return EINTR only if interrupted by a signal. The
> only signal I can see occurring is SIGCHLD, and bash installs the SIGCHLD
> handler with SA_RESTART.
Then, any idea of what can be happening?
- Re: Strange behaviour on 'read' from a pipe, Lluís Batlle i Rossell, 2012/04/01
- Re: Strange behaviour on 'read' from a pipe, Andreas Schwab, 2012/04/01
- Re: Strange behaviour on 'read' from a pipe, Lluís Batlle i Rossell, 2012/04/01
- Re: Strange behaviour on 'read' from a pipe, Chet Ramey, 2012/04/01
- Re: Strange behaviour on 'read' from a pipe,
Lluís Batlle i Rossell <=
- Re: Strange behaviour on 'read' from a pipe, Chet Ramey, 2012/04/01
- Re: Strange behaviour on 'read' from a pipe, Lluís Batlle i Rossell, 2012/04/02
- Re: Strange behaviour on 'read' from a pipe, Lluís Batlle i Rossell, 2012/04/02
- Re: Strange behaviour on 'read' from a pipe, Lluís Batlle i Rossell, 2012/04/02
- Re: Strange behaviour on 'read' from a pipe, Greg Wooledge, 2012/04/02
- Re: Strange behaviour on 'read' from a pipe, Lluís Batlle i Rossell, 2012/04/02