We've jut upgraded from 5.4 to 5.6.1, and tripped over what appears to be a bug: specifically, ".*?\322" as the search target of a regular expression doesn't work (actually, it's any highbit character). 
perl -w -e '$_="Hello there\n"; s/t/\322/; print $_; s/^.*?\322/yes/; 
+print $_'
Hello ̉here
Hello ̉here

[download]
Clearly,in the second line, the correct output is "yeshere". I have determined that "(.*?)\322", "[^\322]*" and ".*\322" all work (but the last obviously means something slightly different). Since we've got this problem in existing code, I'd rather find a patch, or a mechanism for finding the problem areas, rather than having to go through all of our code, checking by eye. Any ideas where to start?

Edit Masem 2001-09-14 - Code tags in examples

In reply to High bit bug in RE? by tommyw

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.