From: Vincent Lefevre <vincent@vinc17.org>
To: zsh-users@zsh.org
Subject: Re: strange behavior
Date: Mon, 11 Apr 2011 16:39:30 +0200 [thread overview]
Message-ID: <20110411143930.GA27818@prunille.vinc17.org> (raw)
In-Reply-To: <20110411142618.GA19503@ypig.lip.ens-lyon.fr>
On 2011-04-11 16:26:18 +0200, Vincent Lefevre wrote:
> On 2011-01-30 14:25:40 -0800, Bart Schaefer wrote:
> > Possible epiphany: zsh prints "zsh: exit 141" like that only if the
> > exit status came from a builtin or shell function (Src/exec.c). For
> > all external commands or subshells it appends the jobtext after the
> > status number (Src/jobs.c). Those are the only PRINTEXITVALUE cases.
> >
> > Thus the exit value of 141 must be coming from one of these places:
> >
> > (1) "read" builtin in the inner loop of "filter"
> > (2) "printf" in the ?* branch of the case in "filter"
> > (3) "echo" in the { ... } expression
>
> I can reproduce the SIGPIPE problem when resizing the terminal window
> while the wrapper is being run. According to strace, it's (3).
and this is because the SIGWINCH seems to interrupt the "read"
(is it a bug?), so that
while read -r $timeout -k -u 0 ch
do
line="$line$ch"
[[ $ch = $'\012' ]] && break
timeout=(-t 0.1)
done
gives an empty string; hence the observed behavior.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
next prev parent reply other threads:[~2011-04-11 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 12:09 Vincent Lefevre
2010-11-15 16:32 ` Vincent Lefevre
2010-11-15 17:24 ` Bart Schaefer
2010-11-16 3:10 ` Vincent Lefevre
2011-01-28 14:44 ` Vincent Lefevre
2011-01-28 15:49 ` Bart Schaefer
2011-01-30 0:37 ` Vincent Lefevre
2011-01-30 22:25 ` Bart Schaefer
2011-01-31 9:11 ` Vincent Lefevre
2011-04-11 14:26 ` Vincent Lefevre
2011-04-11 14:39 ` Vincent Lefevre [this message]
2011-04-11 15:15 ` Peter Stephenson
2011-04-28 11:32 ` Vincent Lefevre
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=20110411143930.GA27818@prunille.vinc17.org \
--to=vincent@vinc17.org \
--cc=zsh-users@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).