Any panic: is by definition a perl bug, as perldiag says. Before reporting it, if possible see if it is still a problem with the latest maintenance release (n.b. make sure it's built with the same options before dismissing the bug as "fixed"), and if it has not already been reported. Both appear to be true in this case.

It's helpful to get the test case as short as possible. In this case: ./perl -e'qr/(?{rand < 5})/' shows the bug (but rand + 5 doesn't). Note that it happens at compile time, not run time.

In reply to Re: "panic: top_env": Is this error resulting from a Perl bug? by ysth
in thread "panic: top_env": Is this error resulting from a Perl bug? by davido

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.