From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: [bug] busyloop upon $=var with NULs when $IFS contains both NUL and a byte > 0x7f
Date: Wed, 30 Nov 2022 09:21:59 +0000 (GMT) [thread overview]
Message-ID: <119794721.6200059.1669800119336@mail.virginmedia.com> (raw)
In-Reply-To: <CAH+w=7bW1ygC0NiL=s7T-U4Ra_3Sr8HtFLnXmbotiTmQDdxWjg@mail.gmail.com>
> On 30/11/2022 04:20 Bart Schaefer <schaefer@brasslantern.com> wrote
> On Tue, Nov 29, 2022 at 6:41 AM Peter Stephenson
> <p.w.stephenson@ntlworld.com> wrote:
> >
> > I guess the obvious thing to do here is any time s doesn't move
> > give up splitting at that point.
>
> I reported the infinite loop back in workers/50472 ("out of memory
> error" thread), although the cause doesn't appear to be exactly the
> same.
>
> I suppose if s doesn't move we could forcibly advance to see if
> another possible split occurs later. Unless there's clearly a way to
> determine that the lack of movement is due to upstream user error
> (such as invalid IFS value in this case)?
Engaging finger-in-the-air mode suggests in a case like this just trying
to be safe is the best we've got, unless we have proof positive we can
do something better in some likely scenario --- Jun may have a feel
for whether there's a potential good (as opposed to not completely
broken) outcome of the case he's looking at, in which case we can be
clever, otherwise I don't think it's worth it.
pws
next prev parent reply other threads:[~2022-11-30 9:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 14:27 Stephane Chazelas
2022-11-29 14:27 ` Jun. T
2022-11-29 14:38 ` Peter Stephenson
2022-11-30 4:20 ` Bart Schaefer
2022-11-30 9:21 ` Peter Stephenson [this message]
2022-12-13 9:50 ` Jun T
2022-12-13 9:49 ` Jun T
2022-12-13 10:13 ` Peter Stephenson
2022-12-13 11:40 ` Jun T
2022-12-13 11:55 ` Peter Stephenson
2023-06-21 4:49 ` Jun T
2022-12-11 19:12 ` Stephane Chazelas
2022-12-13 9:51 ` Jun T
2022-11-30 14:56 ` 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=119794721.6200059.1669800119336@mail.virginmedia.com \
--to=p.w.stephenson@ntlworld.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).