The main problem is finding the particular call to the string eval that is causing the problem. What I do for these situations is:
in reply to Error ... at (eval 75) line 7974.
- use grep (or your code editors search facility) to find all of the calls to eval
- insert print STDERR "before eval: <$sEval>\n" Although in this case you might want to print out only a substring rather than the whole string for evaluation.
- If you don't mind a being a bit wordier, instead of the above, you can insert the following instead print STDERR "before eval \@ line " . __LINE__ . " of file " . __FILE__ . ": <$sEval>\n"
- insert print STDERR "after eval\n"; after each eval.
- Watch what happens
That should at least help you isolate the particular eval that is causing the problem. However, your real issue is a 7000 line file being eval'd at once. Once you know what string is being eval'd, I would recommend that you put the code in a file and test it running as a normally compiled script.
7000+ lines is awfully long for any script or module, even a test script. I usually try to keep them under 1000 lines and no more than 3000 in really unusual circumstances. You might want to think about how you can trim that down by
- moving repetitive code into subroutines
- data into support files
- splitting up the code into separate more focused modules (i.e. test framework modules)