Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Zsh parser infinite loop in chuck from utils.c on malformed input
- X-seq: zsh-workers 41091
- From: Eduardo Bustamante <dualbus@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Zsh parser infinite loop in chuck from utils.c on malformed input
- Date: Wed, 10 May 2017 09:20:47 -0500
- Cc: zsh-workers@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=161JFLC8MeOjrQeRApXDkMXLKKZKCuDHtju4LCFOeww=; b=RJcTa/06g00C44yxnv3sHhllaB+4M7pKGMVb9LwaEsiYPv9KVVCOGQ7njJPkOD3YXR VOo3HhiOgatjGZz8x9YjoAar89MIfowCDtl3VUlpk+Rx0xV6kdO2oxpToqiv7b1dcKiZ Revkf2+HsU3ZyauGnpGFMmt5ft4XlHEqZivck6Yh0W9gNHBpjDUDSn1DQL0yQOIp/2s4 rTmlDmcHpw4FQP4F1ByhMd1e590MJ4SWRD4IqyH/yTXYyWG5LZZ/LR97VviV6xccpajt XDE6OqIcGGoMbgUagHhGfptuAQUyaXYHZm9xG6uKup4k9mYXlz3WxKn651jDS3w5eRwo 85Tg==
- In-reply-to: <170509234322.ZM7806@torch.brasslantern.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CAOSMAuu3oUB7eMu_R8ZBEi2ie+07rfBjTC+EQekrVsYFWH4itw@mail.gmail.com> <170509234322.ZM7806@torch.brasslantern.com>
On Wed, May 10, 2017 at 1:43 AM, Bart Schaefer
<schaefer@xxxxxxxxxxxxxxxx> wrote:
[...]
> This probably should have been a parse error because the { } are not
> balanced, but I'm guessing the parser returns a complete expression
> when it hits EOF. Anyway, parameter expansion is one of the few things
> that happens in noexec, and those %%%% in the flags list mean to treat
> all that garbage as a prompt ... so I suspect it's not actually in an
> *infinite* loop, just one that is going to repeat 3333333333333333333
> times.
I see. Is there a particular reason parameter expansion is performed
when noexec is on, and is there a way to disable expansions too?
(I'm interested in finding parsing problems, so this specific case
will most likely slow down the fuzzing).
Messages sorted by:
Reverse Date,
Date,
Thread,
Author