zsh-workers
 help / color / mirror / code / Atom feed
From: Petros Aggelatos <petrosagg@gmail.com>
To: zsh-workers@zsh.org
Subject: bug with named pipes and process substitution
Date: Tue, 21 Jul 2015 17:25:15 -0700	[thread overview]
Message-ID: <CAA+L57VhrJWyaxpr_iKjkjzYEeEx1YCrEmO02CkAJPtmDwQbsw@mail.gmail.com> (raw)

Hi all,

I encountered a bug when running the following two commands:

mkfifo test_pipe
echo 1 | tee >(cat > test_pipe) | paste - test_pipe

In bash and zsh 5.0.2 it outputs "1 1" and then exits. In zsh 5.0.8
however, it outputs the same thing and hangs forever.

I bisected the repo for the commit that introduced this behaviour and
it was introduced in 3c5732223f65309c6820f15b8519f674bd21185b which
includes the patch from this thread
http://www.zsh.org/mla/workers/2013/msg00569.html

I haven't yet figured out how and what, since I'm not very familiar
with the codebase. I'll try to figure out a patch but if someone can
shed some light on what is going on that would be great.

System info:

$ echo $ZSH_VERSION $ZSH_PATCHLEVEL `uname -mo`
5.0.8 zsh-5.0.8-0-gf0068ed x86_64 GNU/Linux

Best,
Petros


             reply	other threads:[~2015-07-22  0:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22  0:25 Petros Aggelatos [this message]
2015-07-22  9:09 ` Peter Stephenson
2015-07-22  9:58   ` Peter Stephenson
2015-07-22 10:27     ` Peter Stephenson
2015-07-22 14:45       ` Bart Schaefer
2015-07-23  1:03         ` Mikael Magnusson
2015-07-23  1:46           ` Bart Schaefer
2015-07-23  8:15             ` ChangeLog (was Re: bug with named pipes and process substitution) Kamil Dudka
2015-07-23 22:01               ` Daniel Shahaf
2015-07-23  0:32     ` bug with named pipes and process substitution Petros Aggelatos
2015-07-23  9:01       ` Peter Stephenson
2015-07-27 12:25     ` Jun T.
2015-08-08 11:59     ` m0viefreak
2015-08-08 15:21       ` Jun T.

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=CAA+L57VhrJWyaxpr_iKjkjzYEeEx1YCrEmO02CkAJPtmDwQbsw@mail.gmail.com \
    --to=petrosagg@gmail.com \
    --cc=zsh-workers@zsh.org \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).