From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Is this a deadlock waiting to happen?
Date: Sat, 14 Nov 2015 14:47:37 -0800 [thread overview]
Message-ID: <151114144737.ZM1845@torch.brasslantern.com> (raw)
Ray wrote:
body_list=( ${(@f)"$( highlight $filename )"} ) 2>&1 | read _err
I was surprised to find that both $body_list and $_err are set in the
current shell. I had presumed that piping to read would cause the left
side to be forked and the right to be executed in the current shell.
And indeed if I change this to:
body_list=( ${(@f)"$( highlight $filename )"} ) : 2>&1 | read _err
then both the assignment and the ":" command are forked off and only
$_err is available to the current shell.
In the former situation, is it not the case that if the output to stderr
is too large for the OS to buffer in the pipeline, zsh is going to be
deadlocked, because [in the example] "highlight" will be blocked writing
to stderr while zsh is blocked waiting to read stdout from $(...) ?
Where did we optimize out the fork?
next reply other threads:[~2015-11-14 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 22:47 Bart Schaefer [this message]
2015-11-15 17:36 ` Peter Stephenson
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=151114144737.ZM1845@torch.brasslantern.com \
--to=schaefer@brasslantern.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).