zsh-users
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: "Lawrence Velázquez" <larryv@macports.org>
Cc: Russell Harmon <eatnumber1@gmail.com>,  zsh-users@zsh.org
Subject: Re: Segmentation Fault on Stack Overflow
Date: Sat, 04 Jan 2014 02:46:55 +0100	[thread overview]
Message-ID: <878uuwy0vk.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <AF114D5A-7797-4E3F-A34A-A03A0B7E9167@macports.org> ("Lawrence \=\?utf-8\?Q\?Vel\=C3\=A1zquez\=22's\?\= message of "Fri, 3 Jan 2014 20:16:12 -0500")

Lawrence Velázquez wrote:
> On Jan 3, 2014, at 6:36 PM, Frank Terbeck <ft@bewatermyfriend.org> wrote:
>> This is caused by infinite recursion. More recent versions of the shell
>> will react more reasonably:
>> 
>> zsh% function inf() { inf }; inf
>> inf: maximum nested function level reached
>
> What version are you using? I'm seeing the segfault with the latest release.
>
>     % zsh --version
>     zsh 5.0.4 (x86_64-apple-darwin13.0.2)
>     % zsh -c 'function inf() { inf }; inf'
>     zsh: segmentation fault  zsh -c 'function inf() { inf }; inf'
>     %

Huh. I must be remembering something incorrectly. The limit was in place
since sometime in 2000¹. But you might be building with the
‘--disable-max-function-depth’ configuration option.

Otherwise the limit should be in place (it defaults to 1000). If the
limit is in place, and the shell still crashes, it might be another
issue, which I couldn't reproduce then.

Regards, Frank

For the record, I've tried this with an older development version of
zsh: zsh-5.0.2-174-g8a70a98

¹ http://www.zsh.org/mla/workers/2000/msg01390.html


  reply	other threads:[~2014-01-04  1:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 23:03 Russell Harmon
2014-01-03 23:36 ` Frank Terbeck
2014-01-04  1:16   ` Lawrence Velázquez
2014-01-04  1:46     ` Frank Terbeck [this message]
2014-01-05 17:58       ` Peter Stephenson

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=878uuwy0vk.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --cc=eatnumber1@gmail.com \
    --cc=larryv@macports.org \
    --cc=zsh-users@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).