dave_the_m just pushed a set of changes that should fix this. It seems the (deep) cause was an overflow of a sequence counter that reached a magic value.
COP_SEQ_RANGE_LOW _HIGH ----------------- ----- PERL_PADSEQ_INTRO 0 variable not yet introduced: { m +y ($x valid-seq# PERL_PADSEQ_INTRO variable in scope: { m +y ($x) valid-seq# valid-seq# compilation of scope complete: { m +y ($x) }
Looking at the changes involved, I'm not sure whether the eval was necessary to trigger the bug, but that may be due to my lack of understanding the mechanics involved.
In reply to Re: Interpreter eval counter out of bounds
by Corion
in thread Interpreter eval counter out of bounds
by andreas1234567
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |