zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Segmentation Fault on Stack Overflow
Date: Sun, 05 Jan 2014 14:12:08 -0800	[thread overview]
Message-ID: <140105141208.ZM10797@torch.brasslantern.com> (raw)
In-Reply-To: <20140105213341.71d16903@pws-pc.ntlworld.com>

On Jan 5,  9:33pm, Peter Stephenson wrote:
} Subject: Re: Segmentation Fault on Stack Overflow
}
} On Sun, 5 Jan 2014 17:58:31 +0000
} Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
} > It might be possible to do a little better by querying some of the
} > memory-related limits [...]
} 
} What's more, on Linux the resources useful here aren't actually reported by
} getrusage() at the moment.

We discussed this a bit back when we made --disable-max-function-depth.
It's just not the shell's responsibility to manage resources in this
much detail.  Zsh is hardly alone in this:

schaefer[543] bash
schaefer@burner:~$ inf() { inf; }; inf
zsh: segmentation fault (core dumped)  bash


The most I'd suggest is that we experiment with a MAX_FUNCTION_DEPTH
parameter that users could adjust when they have restrictive soft limits
or a small-memory host, etc.


      reply	other threads:[~2014-01-05 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3540501074823477909@gmail297201516>
     [not found] ` <87d2k8y6wn.fsf@ft.bewatermyfriend.org>
     [not found]   ` <AF114D5A-7797-4E3F-A34A-A03A0B7E9167@macports.org>
     [not found]     ` <878uuwy0vk.fsf@ft.bewatermyfriend.org>
     [not found]       ` <20140105175831.4640d8a5@pws-pc.ntlworld.com>
2014-01-05 21:33         ` Peter Stephenson
2014-01-05 22:12           ` Bart Schaefer [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=140105141208.ZM10797@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).