https://bugs.exim.org/show_bug.cgi?id=1803
--- Comment #43 from Nish Aravamudan <[email protected]> --- (In reply to Zoltan Herczeg from comment #39) > (In reply to Zoltan Herczeg from comment #38) > > I mean just print *extra_bump here: > > > > count = pcre_exec(re_bump, extra_bump, subject, > > > > so we can see all of its fields. > > I have to go now. Anyway, if the 0x20 flag is set in extra_bump->flags and > extra_data->mark points to the address of size_offsets then we nailed the > problem. I suspect extra_data->mark is not initialized, or setting the flag > is not intentional. Btw do you know the meaning of 's' in /./us ? I suspect > 'u' is UTF8. I *think* you have hit it on the head, and I'm hoping it's just a PHP bug when the moved to the JIT implementation for split(). From: http://perldoc.perl.org/perlre.html s Treat string as single line. That is, change "." to match any character whatsoever, even a newline, which normally it would not match. Used together, as /ms, they let the "." match any character whatsoever, while still allowing "^" and "$" to match, respectively, just after and just before newlines within the string. And you're right, /u is for unicode. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/pcre-dev
