From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: EILSEQ in the C locale? (Was: $(<nofile) doesn't set $? to non-zero)
Date: Thu, 15 Mar 2018 07:25:50 +0000 [thread overview]
Message-ID: <20180315072550.GB10057@chaz.gmail.com> (raw)
In-Reply-To: <20180315071204.GA10057@chaz.gmail.com>
2018-03-15 07:12:04 +0000, Stephane Chazelas:
[...]
> $ sudo ./Src/zsh -c 'ERRNO=0; v=$(</dev/mem); echo $? $ERRNO $#v'
> zsh:1: error when reading /dev/mem: operation not permitted
> 1 1 1046296
[...]
BTW, when swapping $#v and $ERRNO above, I noticed that I was
seeing some EILSEQ errors even in the C locale because of
"malformed characters".
I wouldn't expect to get those in a C locale or other locales
with single-byte charsets.
$ a=$'\x80' LC_ALL=C zsh -c 'ERRNO=0; echo $#a $ERRNO'
1 84
$ syserror 84
Invalid or incomplete multibyte or wide character
Maybe some optimisation could be done and things like mbstowc()
avoided when MB_CUR_MAX is 1 or something like that?
(here, I beleive my mbstowc() returns EILSEQ in the C locale for
byte values above 0x7f).
(maybe not worth the effort).
--
Stephane
next prev parent reply other threads:[~2018-03-15 7:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180314103335epcas4p30222f0df02adda27cbddbe62075ff9ad@epcas4p3.samsung.com>
2018-03-14 10:32 ` $(<nofile) doesn't set $? to non-zero Stephane Chazelas
2018-03-14 10:54 ` Peter Stephenson
2018-03-14 14:42 ` Stephane Chazelas
2018-03-14 14:50 ` Peter Stephenson
2018-03-15 7:12 ` Stephane Chazelas
2018-03-15 7:25 ` Stephane Chazelas [this message]
2018-03-19 0:09 ` EILSEQ in the C locale? (Was: $(<nofile) doesn't set $? to non-zero) Bart Schaefer
2018-03-15 9:23 ` $(<nofile) doesn't set $? to non-zero Peter Stephenson
2018-03-15 11:10 ` Stephane Chazelas
2018-03-16 8:24 ` Stephane Chazelas
2018-03-14 11:04 ` Stephane Chazelas
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=20180315072550.GB10057@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=p.stephenson@samsung.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).