Thanks for the reply.

I'll put the code through gdb. I've had limited experience with the perl source, as I did managed to get a Perl 4 version running on VMS many years ago.

I'd forgetton about 'out of memory' as a cause, I will definitely look into that. Its also really helpful to know that regexes can cause problems as well, although in this case I would think the segmentation violation would be 'repeatable'.

Unfortunately, the smaller/shorter versions of the code all work correctly. If I re-run the code when the underlying data is exactly identical the segmentation violation is repeatable, but any type of change to the code or the input causes it to significantly move to earlier or later parts of the code.

The code is portable, I've run it on ActiveState's 5.6.1 for NT, and it worked correctly. That's one of the reasons why I think its compiled code that sits inside of one of the modules, but that could also imply that the problem is with 5.6.0. I use a large number of Perl modules, Storable being one, and an older version (2.x) of Berkeley DB.I haven't had any problems with the shorter smaller versions, its only whe it all comes together and runs for a long period of time.

Thanks.

In reply to Re: Re: segmentation violations by Phomer
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.