We are seeing following crash in Perl 5.24.3 version when multiple clients are connected. Each client is a new thread and each thread creates its own perl interpreter.

#0 0x00007f338c774638 in __strchr_sse42 () from /usr/lib64/libc.so.6

#1 0x00007f33654e1d2e in S_init_postdump_symbols () f

#2 0x00007f33654e8468 in S_parse_body ()

#3 0x00007f33654e9016 in perl_parse ()

#4 0x00007f33654a2e77 in MappingRule_intern (event=..., ruleParameter=..., c_AMName=0x7f33400435d8 "AM", b_reset_perl=false, i_timeout=@0x7f334ec327ec: 0)at ../alarm_mapping.cxx:3384

#5 0x00007f33654bfc41 in MappingRule (event=..., ruleParameter=...) at 1.cxx:891

In reply to Crash at perl_parse() function by prabakar.bhatt

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.