The suggestion elsewhere to use Devel::Trace is a good one.

Otherwise, you need to isolate what is causing the segmentation fault.

You might get some useful information by running perl under gdb and getting a backtrace:

box> gdb perl yourscript.pl
gdb> r
...your program runs and then stops with a segmentation fault
...dropping you back to gdb...
gdb> bt
[download]

the displayed backtrace is perl's call stack, it might give some information as to where perl is dying.

You might also have success by trying to find the minimum amount of code needed to cause the segfault. Try commenting out about 1/2 of the module loads (you can use =pod and =cut to comment out a block of code) and do a binary search. Even with a thousand modules, that would only take approx 10 steps.

box> gdb perl yourscript.pl
gdb> r
[download]

I think "yourscript.pl" shoud be after "r", not after "gdb perl".

Thanks, you're right.

I blame too much time spent in the perl debugger recently.

But you are not showing any code, you are not showing any error message, nor are you even telling what you are doing when the segfault happens. So, don't expect a miracle answer.