Edit report at https://bugs.php.net/bug.php?id=70110&edit=1
ID: 70110
Updated by: cmb@php.net
Reported by: bugzilla77 at gmail dot com
Summary: preg_match problem
-Status: Suspended
+Status: Open
Type: Bug
Package: PCRE related
Operating System: *
PHP Version: 7.0.0beta1
-Assigned To: cmb
+Assigned To:
Block user comment: N
Private report: N
New Comment:
Thanks for the reminder â I don't have time for this, though.
Previous Comments:
------------------------------------------------------------------------
[2017-05-03 10:01:02] hristochonov at gmail dot com
cmb@php.net has commented on [2015-08-25 23:56 UTC]:
"Further improvements have to be postponed until PHP 7.1 at least,
so I'm suspending the ticket for now."
PHP 7.1.0 has been released on 01 Dec 2016. It will be great if it would be possible to bring the
issue forward now. We are experiencing this bug pretty often and have to always manually turn off
PCRE-JIT in code for known regular expressions going to crash.
------------------------------------------------------------------------
[2016-07-20 19:37:37] cmb@php.net
Related To: Bug #72632
------------------------------------------------------------------------
[2016-07-04 14:12:15] cmb@php.net
Related To: Bug #70699
------------------------------------------------------------------------
[2015-08-25 23:56:23] cmb@php.net
After some discussion on the internals list[1], the current stance
is to stick with this behavior for now, i.e. return FALSE if the
regex can't be executed due to JIT limitations, and make that info
available via preg_last_error(), see <https://3v4l.org/IWGam>.
Further improvements have to be postponed until PHP 7.1 at least,
so I'm suspending the ticket for now.
[1] <http://markmail.org/thread/6bcffpbcobyi3ln7>
------------------------------------------------------------------------
[2015-08-13 11:26:16] me at kelunik dot com
There's an even easier case that fails:
preg_match('~(a)*~', str_repeat('a', 5431), $match);
http://3v4l.org/CGSqa
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=70110
--
Edit this bug report at https://bugs.php.net/bug.php?id=70110&edit=1