From: Herbert Xu <herbert@gondor.apana.org.au>
To: Nathan Mills <the.true.nathan.mills@gmail.com>
Cc: DASH Mailing List <dash@vger.kernel.org>
Subject: Re: I found multiple crash bugs in Dash v0.5.12-115-gb4ef25d
Date: Sun, 14 Sep 2025 08:51:28 +0800 [thread overview]
Message-ID: <aMYRkII_1nI--lPF@gondor.apana.org.au> (raw)
In-Reply-To: <CALjJ9ccRuGV9fmydBvwzOua_om7QVoro-nSA-pv+9-nX1KLfGA@mail.gmail.com>
On Fri, Aug 29, 2025 at 07:40:16PM -0700, Nathan Mills wrote:
>
> *Crash v0.5.12-gb4ef25d_try2#5: stack-overflow. cmdloop calls
> evaltree, which calls evalcommand, which calls evalfun, which calls
> evaltree, etc. Dash crashes when reaching 22,448 stack frames deep on
> my machine.
>
> **Crash v0.5.12-gb4ef25d_try2#5: stack-overflow **
>
> Base64'd
> SDsJSCgpAEg7CUgAgH9KSCQj6jw+JF8kEGdISDsJSDxIb3JlLH8AgP+A/yM/Cg==
>
> Minimized (assume the file "empty" does not exist):
> ```
> touch empty
> src/dash -c 'H()H;H<empty'
> ```
This is to be expected. You're doing infinite recursion, of course
it will eventually fail when the stack is exhausted.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2025-09-14 0:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALjJ9ccRuGV9fmydBvwzOua_om7QVoro-nSA-pv+9-nX1KLfGA@mail.gmail.com>
2025-09-13 9:59 ` [PATCH] parser: Skip parsing of old-style command substitution here-doc marker Herbert Xu
2025-09-13 13:18 ` [PATCH] expand: Check for NUL before parsing range expression in pmatch Herbert Xu
2025-09-13 13:34 ` I found multiple crash bugs in Dash v0.5.12-115-gb4ef25d Herbert Xu
2025-09-13 13:45 ` [PATCH] parser: Fix USTPUTC overflow for new-style command substition here-doc marker Herbert Xu
2025-09-13 14:06 ` I found multiple crash bugs in Dash v0.5.12-115-gb4ef25d Herbert Xu
2025-09-13 14:29 ` Harald van Dijk
2025-09-14 0:44 ` [PATCH] expand: Do not use memcmp on strings Herbert Xu
2025-09-14 0:51 ` Herbert Xu [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=aMYRkII_1nI--lPF@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=dash@vger.kernel.org \
--cc=the.true.nathan.mills@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox