From: Vincent Lefevre <vincent@vinc17.net>
To: zsh-workers@zsh.org
Cc: Bart Schaefer <schaefer@brasslantern.com>
Subject: Re: [BUG] builtin echo doesn't check write error
Date: Thu, 24 Jun 2021 11:07:08 +0200 [thread overview]
Message-ID: <20210624090708.GA172975@zira.vinc17.org> (raw)
In-Reply-To: <20210624084739.GB170692@zira.vinc17.org>
On 2021-06-24 10:47:39 +0200, Vincent Lefevre wrote:
> Note also about the bug in echo/print/etc., this actually seems
> to affect *all* builtins. For instance:
>
> zira% (exec >&-; echo)
> zsh: write error: bad file descriptor
> zira% (exec >&-; echo >&-)
> zira% (exec >&-; print)
> zsh: write error: bad file descriptor
> zira% (exec >&-; print >&-)
> zira% (exec >&-; printf "\n")
> zsh: write error: bad file descriptor
> zira% (exec >&-; printf "\n" >&-)
> zira% (exec >&-; pwd)
> zsh: write error: bad file descriptor
> zira% (exec >&-; pwd >&-)
> zira% (exec >&-; history)
> zsh: write error: bad file descriptor
> zira% (exec >&-; history >&-)
> zira%
That was about the error messages. But in all cases, the exit status
is 0:
zira% (exec >&-; echo; echo $? >&2)
zsh: write error: bad file descriptor
0
zira% (exec >&-; echo >&-; echo $? >&2)
0
zira% (exec >&-; print; echo $? >&2)
zsh: write error: bad file descriptor
0
zira% (exec >&-; print >&-; echo $? >&2)
0
zira% (exec >&-; pwd; echo $? >&2)
zsh: write error: bad file descriptor
0
zira% (exec >&-; pwd >&-; echo $? >&2)
0
zira% (exec >&-; history; echo $? >&2)
zsh: write error: bad file descriptor
0
zira% (exec >&-; history >&-; echo $? >&2)
0
The other shells differ, but for ksh, posh and busybox sh, in an
inconsistent way (I assume that this is a bug in these shells):
$ zsh -c 'exec >&-; echo; echo $? >&2; pwd; echo $? >&2'
zsh:1: write error: bad file descriptor
0
zsh:1: write error: bad file descriptor
0
$ sh -c 'exec >&-; echo; echo $? >&2; pwd; echo $? >&2'
sh: 1: echo: echo: I/O error
1
sh: 1: pwd: pwd: I/O error
1
$ bash -c 'exec >&-; echo; echo $? >&2; pwd; echo $? >&2'
bash: line 1: echo: write error: Bad file descriptor
1
bash: line 1: pwd: write error: Bad file descriptor
1
$ yash -c 'exec >&-; echo; echo $? >&2; pwd; echo $? >&2'
echo: cannot print to the standard output: Bad file descriptor
1
pwd: cannot print to the standard output: Bad file descriptor
1
$ busybox sh -c 'exec >&-; echo; echo $? >&2; pwd; echo $? >&2'
sh: write error: Bad file descriptor
1
1
(for busybox sh, the inconsistency is on the presence of the
error message).
$ ksh93 -c 'exec >&-; echo; echo $? >&2; pwd; echo $? >&2'
1
0
$ mksh -c 'exec >&-; echo; echo $? >&2; pwd; echo $? >&2'
1
0
$ posh -c 'exec >&-; echo; echo $? >&2; pwd; echo $? >&2'
1
0
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
prev parent reply other threads:[~2021-06-24 9:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 14:09 Vincent Lefevre
2021-06-09 14:17 ` Vincent Lefevre
2021-06-09 15:33 ` Stephane Chazelas
2021-06-09 15:40 ` Stephane Chazelas
2021-06-09 15:59 ` Stephane Chazelas
2021-06-09 16:13 ` Bart Schaefer
2021-06-09 18:16 ` Stephane Chazelas
2021-06-10 8:11 ` Vincent Lefevre
2021-06-24 8:47 ` Vincent Lefevre
2021-06-24 9:07 ` Vincent Lefevre [this message]
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=20210624090708.GA172975@zira.vinc17.org \
--to=vincent@vinc17.net \
--cc=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).