zsh-workers
 help / color / mirror / code / Atom feed
From: Kamil Dudka <kdudka@redhat.com>
To: "Jérémie Roquet" <jroquet@arkanosis.net>
Cc: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: unbounded recursive call in a shell script crashes zsh
Date: Tue, 11 Apr 2017 16:38:31 +0200	[thread overview]
Message-ID: <1569411.Kln6y2GJnM@kdudka-nb> (raw)
In-Reply-To: <CAFOazAM_2dX4F-5i5ER61EFf8WmO-43CnNbJq3CZWQHdaG78=A@mail.gmail.com>

On Tuesday, April 11, 2017 16:01:10 Jérémie Roquet wrote:
> 2017-04-11 15:29 GMT+02:00 Jérémie Roquet <jroquet@arkanosis.net>:
> > 2017-04-11 15:00 GMT+02:00 Kamil Dudka <kdudka@redhat.com>:
> >> The following shell script crashes zsh (tested with zsh-5.3.1-90-
g63f086d):
> >>     function foo() {
> >>     
> >>         if true; then
> >>         
> >>             foo
> >>         
> >>         fi
> >>     
> >>     }
> >>     
> >>     foo
> > 
> > That's interesting:
> > 
> > $ zsh -c 'foo() { foo }; foo'
> > foo: maximum nested function level reached
> > 
> > $ zsh -c 'foo() { if true; then foo; fi }; foo'
> > Segmentation fault
> 
> That looks like a stack overflow…
> 
> Doing either of the following fixed the issue for me:
>  - recompile after “./configure --enable-max-function-depth=500”
> (default is 1000);
>  - execute after “ulimit -s 16384” (default for me was 8192).

Thanks!  I can confirm that the error is handled properly after increasing
the limit for stack allocation.

So the difference is caused by the fact that recent versions of zsh are
more hungry on stack, so the stack allocation limit is exceeded before the 
shell call recursion limit is reached.

Kamil

> Best regards,


  reply	other threads:[~2017-04-11 14:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 13:00 Kamil Dudka
2017-04-11 13:29 ` Jérémie Roquet
2017-04-11 14:01   ` Jérémie Roquet
2017-04-11 14:38     ` Kamil Dudka [this message]
2017-04-12  2:12       ` Bart Schaefer
2017-04-12  7:30         ` Kamil Dudka
2017-04-12 22:11           ` Bart Schaefer
2017-04-13 14:30             ` Kamil Dudka
2017-04-13 15:21               ` Jérémie Roquet
2017-04-13 16:01                 ` Jérémie Roquet
2017-04-15 16:14                   ` Bart Schaefer
2017-04-16 18:56                     ` Daniel Shahaf
2017-04-16 21:00                       ` Bart Schaefer
2017-04-16 23:12                         ` Daniel Shahaf
2017-04-17  0:17                           ` Bart Schaefer
2017-04-18 13:54                   ` Kamil Dudka
2017-04-19 21:01                     ` Bart Schaefer

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=1569411.Kln6y2GJnM@kdudka-nb \
    --to=kdudka@redhat.com \
    --cc=jroquet@arkanosis.net \
    --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).