Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Segmentation Fault on Stack Overflow
- X-seq: zsh-workers 32236
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: "Zsh Hackers' List" <zsh-workers@xxxxxxx>
- Subject: Re: Segmentation Fault on Stack Overflow
- Date: Sun, 05 Jan 2014 14:12:08 -0800
- In-reply-to: <20140105213341.71d16903@pws-pc.ntlworld.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: <3540501074823477909@gmail297201516> <87d2k8y6wn.fsf@ft.bewatermyfriend.org> <AF114D5A-7797-4E3F-A34A-A03A0B7E9167@macports.org> <878uuwy0vk.fsf@ft.bewatermyfriend.org> <20140105175831.4640d8a5@pws-pc.ntlworld.com> <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@xxxxxxxxxxxx> 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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author