From: Leopold Toetsch <[EMAIL PROTECTED]>
Date: Mon, 17 Jul 2006 11:50:35 +0200
Am Montag, 17. Juli 2006 03:30 schrieb Bob Rogers:
> BTW, it doesn't seem right that I can run Parrot for only a second or
> two and get more than 300K stack frames deep. Isn't there a way to
> limit the stack to something sane, since more than a few MB of C stack
> usage is a pretty sure sign of a Parrot bug?
'man ulimit' is your friend.
It certainly is; thank you.
But what I really meant was: Shouldn't Parrot do a 'setrlimit' on
itself in order to detect these sorts of bugs sooner, and more usefully?
Or, maybe 'ulimit -s' would be appropriate before running test cases?
-- Bob
