Suggestion:

Try to isolate when it happens. Ie. add a warn statement just before your exit. (warn not print or disable buffering on stdout.)

If that is printed before you see the segfault, it is probably happening when perl is trying to free some memory.(*)

One way to verify that is to use POSIX::_exit() instead of exit. That will bypass perl's cleanup of memory. If that avoids the segfault, don't stop there. Try and isolate the cause further.

One way to do that is to explicitly undef everything that exists in your program at point where you normally exit. Go through your program and explicitly call undef( $var ) on every object and datastructure in your program. If doing so causes the segfault before you see your previously added warn 'Exiting' message, you've probably found the culprit so it's just a case of isolating which it is.

Comment out half of your undefs and try again. If you still get the segfault before the exiting, it's in the other half, so comment out half of the remaining undefs.

If not, uncomment the first half and comment out the second.

Continue that until (with luck), you get down to the one undef that causes the segfault. If you are successful in so isolating the cause, try and recreate the problem in a small, standalone program using whatever module or datastructure is at causing it.

If the above procedure fails to isolate a cause, then the next step would be to cut stuff out of the program bit by bit until the segfault no longer happens. Or, you could look to building a debug version of perl and/or using a debugger to track down the cause, but that requires a whole host of other skills.

(*)If not, litter the program with warn statements to see where the segfault is occuring. Another method might be to run the program under that auspices Devel::Trace in the hope that might show you where the problem is occuring. Be warned, the program will run very, very slowly.