From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: unbounded recursive call in a shell script crashes zsh
Date: Sun, 16 Apr 2017 18:56:28 +0000 [thread overview]
Message-ID: <20170416185628.GA25858@fujitsu.shahaf.local2> (raw)
In-Reply-To: <170415091456.ZM22606@torch.brasslantern.com>
Bart Schaefer wrote on Sat, Apr 15, 2017 at 09:14:56 -0700:
> If not for the variable thrown in by the compiler options it might be
> possible for zsh to estimate a value for max function depth at the
> time it starts up, by examining the current limits,
>
Hmm. Would it work to measure the stack space used, by declaring
a local variable in main(), stashing its address in a global write-once
variable, and then subtracting the address of a function-local variable
from the global? That is:
extern const void *top_of_stack;
main() {
const int x = …;
top_of_stack = &x;
⋮
}
foo() {
int x;
printf("Stack space in use: %llu\n", (unsigned long long)(top_of_stack - &x));
}
(I somewhat expect this to be a bad idea...)
> but there's also no guarantee that the limit settings reflect the
> actual amount of stack available.
next prev parent reply other threads:[~2017-04-16 19:02 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
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 [this message]
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=20170416185628.GA25858@fujitsu.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--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).