Another thought occurred to me: It may be worth your while to use a tracing module (e.g. Devel::Trace) and run your program so you can see the last few operations that occurred. Then you might see an interesting place to put a breakpoint in Parse::RecDescent and find out what's driving it mad.
(I had just opened Parse::RecDescent in my editor, thinking I'd give it a brief scan to see what bits of code may be generating the message, but 6000+ lines of code can be a bit much to wade through.)
...roboticus
In reply to Re^3: An odd (lack of...) error message(s) from Parse::RecDescent
by roboticus
in thread [SOLVED; FALSE-ALARM] An odd (lack of...) error message(s) from Parse::RecDescent
by locked_user sundialsvc4
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |