https://bugs.exim.org/show_bug.cgi?id=2527
--- Comment #10 from Philip Hazel <ph10@???> ---
Well, that took some finding. Turned out that the bug was in the UTF-16
checking code. It returned an incorrect offset for the point at which the
string was invalid, causing the search after the invalidity to start one code
unit too far along. This bug has been present for a very long time, but only
really matters for PCRE2_MATCH_INVALID_UTF. I've fixed it in r1226. Thanks for
all the testing you are doing.
--
You are receiving this mail because:
You are on the CC list for the bug.
