Clinton A. Pierce <[EMAIL PROTECTED]> wrote:
Found the bug. Mostly MEA CULPA. A thousand pardons to the good Parrot folk.
When calling a sub like this:
.arg 0 call _foo
It's probably a good thing to take the 0 off the stack at some point.
Thanks again for your bug report and thorough checking all kind of parrot limits.
I've added a check for too deeply nested stacks now. Your first test program now bails out at:
25342 Stack 'User' too deep
The limit is currently fixed at 100 chunks, but could easily be changed with a new opcode, e.g. stack_limit <.Stack>, limit.
This sounds like a good option, though 100 might be a bit small, since I plan on giving new frames on pushes to COW'd stack chunks. (No reason not to (well, besides the performance hit) and it makes some coroutine stuff easier)
I probably ought to get started on the stack-chunk-as-PMC patch for garbage collection of stack frames. :)
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
