Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91243
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain cschneid.com from 195.226.6.51 cause and error)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: <79F03701-9083-439B-A9D1-43E24C99CF13@cschneid.com>
Date: Wed, 17 Feb 2016 14:06:41 +0100
To: PHP internals <internals@lists.php.net>
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: PCRE jit bug with UTF-8 and lookbehind assertion
From: cschneid@cschneid.com (Christian Schneider)

Hi there,
we just ran into a version of the bug "JIT bug with lookbehind =
assertion":
	https://bugs.exim.org/show_bug.cgi?id=3D1189

To reproduce it you can use
	php -n -r 'ini_set("pcre.jit", 0); echo =
preg_replace("/\b(11|21|41)\b/u", "z", "x=C2=B011\n");'
vs.
	php -n -r 'ini_set("pcre.jit", 1); echo =
preg_replace("/\b(11|21|41)\b/u", "z", "x=C2=B011\n");'

Since the PCRE bug report dates from 2011-12-27 and is still marked NEW =
I wonder if it would be safer for PHP to disable pcre.jit in the =
recommended php.ini configuration files.

Also: Does anyone know who might be able/willing to look at the upstream =
bug?

Regards,
- Chris