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

In reply to Re: segmentation violations by Abigail-II
in thread segmentation violations by Phomer

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.