It looks like the problem is this part of your pattern: .+. This, being greedy, will eat up everything up to the last possible occurrance of the rest of your pattern. You actually shouldn't need either the \G anchor or that .+ part because the /g flag means that each time through the loop it will pick up where it left off after the last match.

Update: Also, you should be able to use plain old \n instead of that funky \x0D?\x0A so long as the log is generated on the same OS you're running the Perl program on. If not, just run dos2unix or unix2dos as appropriate.

In reply to Re: regex issues with /gc in log analysis... by Errto
in thread regex issues with /gc in log analysis... by EvanK

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.