Other respondents have suggested that you may be running out of memory, but that shouldn't normally cause a coredump. Coredumps tend to be quite specific to platform and perl version, so a useful starting point would be to show the output of perl -V.
Of the modules you are using, the most system-sensitive is actually Time::HiRes, so it might be worth checking that you have the latest version installed.
Since you presumably have a core file, the next useful thing to do would be to show it to a C-level debugger and ask for a backtrace. However the usefulness of the information may be limited if your perl isn't built with debugging symbols; in that case it might be worth trying to build a perl with debugging enabled and trying again.
Hugo
In reply to Re: Segment Fault(Core Dump)
by hv
in thread Segment Fault(Core Dump)
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |