Well, if you don't know at all where the segmentation violation is happening, you could always try running the program in a debugger. For instance, with gdb or with valgrind. But that will require some knowledge of perl to make sense of the output.

There are some known cases of segmentation violation in Perl. Out of memory, and compilation of syntactically unvalid regexes are two things I know. But there can be a million unknown cases. Unless you can isolate the problem to a small piece of code, there isn't much we can do.

Of course, one of the things you can do is to see whether you get the segmentation violation with 5.6.1 or 5.8.0. If not, then the problem was already solved.

Abigail