Re: An odd (lack of...) error message(s) from Parse::RecDescent

Three words: Divide and conquer.

In other words, take the grammar tree, and replace one of the subtrees with a trivial production, and see if the error goes away. If the error remains, then you've shortened the grammar to a smaller example. If not, you've found the production that contains the error, and you should be able to put that production at the root of your script and remove the rest of the grammar.

Lather, rinse and repeat. You'll either: (a) have a short example (which would be easier anonymize) that you can post, or (b) trip over the answer.

...roboticus

Comment on Re: An odd (lack of...) error message(s) from Parse::RecDescent

Replies are listed 'Best First'.
Re^2: An odd (lack of...) error message(s) from Parse::RecDescent by locked_user sundialsvc4 (Abbot) on Sep 16, 2010 at 13:39 UTC
That’s what I’ll be doing today ... and when I find it, I will post. The nature of the output ... blanks and colon-characters, with the colons (actually) not always quite in the same column ... almost looks like it is part of, or taken from, some part of the grammar. It is, obviously, “nonsensical, but not random.” So, as you say, “there’s really only way to find this,” and as soon as I do, I will give a full report. All in the name of saving a few of the next person’s hair follicles. Thanks, all. “There comes a glorious time in every day when one must stop writing computer software, and start drinking good dark beer.”
Re^3: An odd (lack of...) error message(s) from Parse::RecDescent by roboticus (Chancellor) on Sep 16, 2010 at 14:26 UTC
sundialsvc4: 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	[reply]