Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100699
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.178 as permitted sender)
MIME-Version: 1.0
Sender: giovanni.g@gmail.com
In-Reply-To: <CA+kxMuRdwo2oseVdbZX30e-a7ixOWTDjB4BySJvivkHvJL0kVQ@mail.gmail.com>
References: <CAML1Pf51qWjsMajxSriBDphB6fq_YaJabHpyptv-6fz1odFPEw@mail.gmail.com>
 <CA+kxMuRdwo2oseVdbZX30e-a7ixOWTDjB4BySJvivkHvJL0kVQ@mail.gmail.com>
Date: Mon, 18 Sep 2017 14:05:53 +0200
Message-ID: <CAML1Pf5SJxvxFhCrJxqUw7ja8HR1c2EzJBCmcr9oP+7FDFZ3tQ@mail.gmail.com>
To: Dan Ackroyd <danack@basereality.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="f4030436516e7da94505597590a9"
Subject: Re: [PHP-DEV] PCRE JIT broken in PHP 7.2
From: giovanni@giacobbi.net (Giovanni Giacobbi)

--f4030436516e7da94505597590a9
Content-Type: text/plain; charset="UTF-8"

On 18 September 2017 at 13:46, Dan Ackroyd <danack@basereality.com> wrote:

> On 18 September 2017 at 12:28, Giovanni Giacobbi <giovanni@giacobbi.net>
> wrote:
> >
> > just an heads up, I started testing my project with PHP 7.2.0RC2 but it
> was
> > causing a segmentation fault.
>
> Even if you think bugs are urgent enough to email the internals list -
> please open a bug report at bugs.php.net first, so that people can
> response to it without spamming the list.
>
>
The attitude in this ml is always very challenging.

Yes, a bug that completely brokens a working environment when upgrading
from 7.1.9 to 7.2.0, while we are in RC2 stage, I think it's quite urgent
and requires attention.

Anyway, the bug has been filed as #75223

> If you need any further information let me know.
>
> "See how to get a backtrace in case of a crash":
> https://bugs.php.net/bugs-generating-backtrace.php
>
>
I believe who worked on the PCRE support (the problem is either the bundled
pcre library update or the JIT fast path API), might have enough
information, otherwise if they kindly request the backtrace I will provide
it.

Of course I'm also fine sticking with 7.1.9 and waiting for someone else to
incur in the problem and wait until it's fixed.

-- 
Giovanni Giacobbi

--f4030436516e7da94505597590a9--