Monks, I come seeking wisdom.
The issue is quite simple, really, although I am at a loss as to how to proceed. I have a Perl script, perhaps too long to post, and perl itself is dying with Floating point exception and after much instrumentation, I still have no real idea why, where or when, due to evals within evals (and no, I'm not trying to beat obfuscation records) and I have a feeling that may be the cause).
It only dies after several minutes of CPU time (several million iterations), and so short of generating several gigabytes of trace, I don't know how to come closer to the cause.
The question is simple: what kind of tools are available to help me pinpoint and isolate the problem so that I can start working on a simpler test case. For instance, can I trap a signal (which one?) and is there a way to determine the current source line of execution?
In reply to Floating point exception by grinder
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |