I'm running Slackware64-current and have recently installed all of the newest updates. Also running GCC-5.2 and KDE-5 from Alien. After applying the latest Slack updates perl suddenly stopped working. Perl -v returns the version info but anything else I try that uses perl just seg faults. eg -
root@missi:/var/log$ shorewall start Compiling using Shorewall 5.0.1.1... /usr/share/shorewall/lib.cli-std: line 369: 11333 Segmentation fault + $PERL $debugflags $pc $options $@
or
root@missi:/var/log$ perldoc perl Segmentation fault
or
root@missi:/var/log$ perl -MCPAN -e 'shell' Segmentation fault

I uninstalled perl and rebuilt and installed to no avail.

No helpful info in syslog or messages other than the fact that perl seg faulted.

I haven't got a clue how to trouble shoot this and would appreciate any helpful suggestions that come to mind. Thanks in advance.


In reply to Perl 5.22 no longer works by 3rensho

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.