Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91792
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.53 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
In-Reply-To: <5E36AA30-831F-44BE-A148-8720B8E87E96@heroku.com>
Date: Sun, 20 Mar 2016 22:09:35 +0100
Cc: Christoph Becker <cmbecker69@gmx.de>,
 Pierre Joye <pierre.php@gmail.com>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <94A89B0F-48BB-4DD8-A26B-3B6D2C8C2C9F@heroku.com>
References: <55B0CADD.8000807@gmx.de> <CAEZPtU7aPzPQ=DL5fn9fOEuU_hySm5WXUkbjFw+Sq0T5xNfb3A@mail.gmail.com> <55B136BE.8010006@gmx.de> <046401d0c644$9cf76880$d6e63980$@belski.net> <55B2B78A.4080202@gmx.de> <048001d0c665$ed19ec40$c74dc4c0$@belski.net> <55B2D779.9090409@gmx.de> <04d301d0c6e5$6b28f0c0$417ad240$@belski.net> <55B3B2E6.7080905@gmx.de> <056e01d0c7d9$b1edd990$15c98cb0$@belski.net> <55B559C7.9060304@gmx.de> <064301d0c85f$5260ac60$f7220520$@belski.net> <55C008B1.2050008@gmx.de> <05ec01d0ce97$4ee7c4e0$ecb74ea0$@belski.net> <55C09EE2.7010400@gmx.de> <063f01d0cec2$91b9baf0$b52d30d0$@belski.net> <55C0F908.2050708@gmx.de> <068e01d0cefb$6ffba3e0$4ff2eba0$@belski.net> <A428AF35-A176-404D-888C-7541100155B2@heroku.com> <016e01d17ef7$cd8a2660$689e7320$@belski.net> <25D67B35-88FF-4A5C-9421-BAF482B32A96@heroku.com> <036501d17fc3$d51357e0$7f3a07a0$@belski.net> <5E36AA30-831F-44BE-A148-8720B8E87E96@heroku.com>
To: Anatol Belski <anatol.php@belski.net>
Subject: Re: [PHP-DEV] PCRE JIT stack size limit
From: dz@heroku.com (David Zuelke)

> On 17.03.2016, at 05:22, David Zuelke <dz@heroku.com> wrote:
>=20
>> On 16.03.2016, at 21:38, Anatol Belski <anatol.php@belski.net> wrote:
>>=20
>> Hi,
>>=20
>>> -----Original Message-----
>>> From: David Zuelke [mailto:dz@heroku.com]
>>> Sent: Tuesday, March 15, 2016 11:58 PM
>>> To: Anatol Belski <anatol.php@belski.net>
>>> Cc: Christoph Becker <cmbecker69@gmx.de>; Pierre Joye
>>> <pierre.php@gmail.com>; PHP internals <internals@lists.php.net>
>>> Subject: Re: [PHP-DEV] PCRE JIT stack size limit
>>>=20
>>> Sure. So composer creates patterns to parse a file dynamically; I =
have not
>>> figured out why it only happens for some composer.json files (or =
maybe it
>>> happens for all of them and I just have not noticed), but this =
example here I
>>> extracted from a reproducibly failing "composer require" run; it =
runs into the JIT
>>> stack size limit on PHP 7 while it works fine on 5.x:
>>>=20
>>> https://gist.github.com/dzuelke/cc64a630c14416eda3e9
>>>=20
>> I've just tried this on Debian Jessie and on Windows with the latest =
7.0.x builds, in both cases the error is PREG_BACKTRACK_LIMIT_ERROR. I'd =
be next asking you to check the configuration. Runtime like system or =
ini, or build config can affect this. Anyway, I don't see an issue with =
PCRE JIT at the moment.
>=20
> Sorry, I simplified the example too far. Updated it again to throw a =
JIT stack limit error again (but works fine with "php -dpcre.jit=3D0"):
>=20
> =
https://gist.github.com/dzuelke/cc64a630c14416eda3e9/de7b7293798ac57b4f75d=
822dc22a625be0fe9df

Were you able to reproduce this? :)

David