Thorsten Glaser t...@mirbsd.de wrote:
|Steffen Nurpmeso dixit:
|An interactive shell or '/usr/bin/mksh -c exec ./t.sh' limits
|the storm in the same way that bash(1) does
|Running 'bash t.sh' shows…
|
|au
|au
|au
|after zap
|au
|au
|au
|au
|au
[ au]
|exit
|au
|
|… weirdly
Steffen Nurpmeso dixit:
I would prefer seeing a stack recursion limit exceeded or
similar before SIGSEGV happens because of recursive functions,
Yeah, but I have no idea how to do that. If you find one… tell me.
bye,
//mirabilos
--
“It is inappropriate to require that a time represented as
Thorsten Glaser t...@mirbsd.de wrote:
|Steffen Nurpmeso dixit:
|I would prefer seeing a stack recursion limit exceeded or
|similar before SIGSEGV happens because of recursive functions,
|
|Yeah, but I have no idea how to do that. If you find one… tell me.
Anyway i'm thankful i was worth an
Steffen Nurpmeso dixit:
a different, even older message: use a recursion counter, how
wacky that may be.
Nah. It’s either too high (with the obvious effect) or, like
PHP’s, way too low (1000 just doesn’t cut it in may legitimate
cases). And even a too-low one can still segfault if the user
plays
Hello Thorsten,
i wrote a buggy shell script similar to the crap below, but it
crashed mksh(1):
cat t.sh _EOT
trap echo au; kill $$ TERM
trap echo exit EXIT
zap=`kill -TERM $$`
echo after zap
exit
_EOT
An interactive shell or '/usr/bin/mksh -c exec ./t.sh' limits
the storm in the
