|Problems? Is your data what you think it is?|
Re^3: Error ... at (eval 75) line 7974.by BrowserUk (Pope)
|on Apr 14, 2009 at 11:59 UTC||Need Help??|
Have you tried enabling trace? our $::RD_TRACE = 1;
If that output doesn't help you track back to the C/C++ code that's being mis-parsed, then you could try my old standby:
You'll want to ensure you have plenty of free diskspace and something else to do for a few hours--sleeping's good. Cos a program that would run for a few seconds normally, can take hours. But generally, especially if you can make the error fatal (maybe Fatal?), then when it stops the last couple of hundred lines of the trace tell you everything you need to know.
If you want to get sophisticated, you can turn the tracing off at the top of your program and then turn it on just before whatever line of your code instigated the code that issues the warning. It can get you there more quickly. Good luck.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.