Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: [bug] busyloop upon $=var with NULs when $IFS contains both NUL and a byte > 0x7f

X-seq: zsh-workers 51085
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: zsh-workers@xxxxxxx
Subject: Re: [bug] busyloop upon $=var with NULs when $IFS contains both NUL and a byte > 0x7f
Date: Tue, 29 Nov 2022 20:20:01 -0800
Archived-at: <https://zsh.org/workers/51085>
In-reply-to: <351204342.6213761.1669732685914@mail.virginmedia.com>
List-id: <zsh-workers.zsh.org>
References: <20221118142717.t4elzrigjeizjm6w@chazelas.org> <AD3B3716-F348-4C93-981F-8B8DD624C37D@kba.biglobe.ne.jp> <351204342.6213761.1669732685914@mail.virginmedia.com>

On Tue, Nov 29, 2022 at 6:41 AM Peter Stephenson
<p.w.stephenson@xxxxxxxxxxxx> 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)?

Follow-Ups:
- Re: [bug] busyloop upon $=var with NULs when $IFS contains both NUL and a byte > 0x7f
  - From: Peter Stephenson

References:
- [bug] busyloop upon $=var with NULs when $IFS contains both NUL and a byte > 0x7f
  - From: Stephane Chazelas
- Re: [bug] busyloop upon $=var with NULs when $IFS contains both NUL and a byte > 0x7f
  - From: Jun. T
- Re: [bug] busyloop upon $=var with NULs when $IFS contains both NUL and a byte > 0x7f
  - From: Peter Stephenson

Messages sorted by: Reverse Date, Date, Thread, Author