First, install Devel::Trace and run the program with perl -d:Trace foo.pl to see if the problem occurs during runtime. If it does, you at least know which line is called at that point.
However, your problem sounds like a bug in perl itself. Use a debugger (like gdb) on the dumped core. This requires some experience or a good guide. Guides can be found with Google.
You can also send the core file to someone who knows what to do. I don't know if the other person would need to use the same platform.
Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }
In reply to Re: Techniques for isolating bugs in perl
by Juerd
in thread Techniques for isolating bugs in perl
by Ytrew
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |