Parrot should limit its own stack usage?

[Bob Rogers]

   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

Re: Parrot should limit its own stack usage?

[Chip Salzenberg]

On Mon, Jul 17, 2006 at 09:26:12PM -0400, Bob Rogers wrote:
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?

Running the test suite (or at least most of it) under ulimit is indeed a
good idea.  Whoever jumps in on this, please be prepared to adjust the value
as reports come in from the field.  :-)
-- 
Chip Salzenberg [EMAIL PROTECTED]