Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:91422
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error)
To: =?utf-8?Q?'=C3=81ngel_Gonz=C3=A1lez'?= <keisial@gmail.com>
Cc: "'Christian Schneider'" <cschneid@cschneid.com>,
	"'PHP internals'" <internals@lists.php.net>
References: <79F03701-9083-439B-A9D1-43E24C99CF13@cschneid.com> <012501d16a24$a230d050$e69270f0$@belski.net> <031b01d16aee$645ef340$2d1cd9c0$@belski.net> <56C90452.7040206@gmail.com> <001001d16c94$954769e0$bfd63da0$@belski.net> <56CF6009.9070704@gmail.com>
In-Reply-To: <56CF6009.9070704@gmail.com>
Date: Thu, 25 Feb 2016 21:29:14 +0100
Message-ID: <06b001d1700b$34a40290$9dec07b0$@belski.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQCki6lgPnkuaeTfOvRULIcZxGmWEQIEFtpNAWCMn0wCadtqGwIy/CLmAq/u1LKhQXM1kA==
Content-Language: en-us
Subject: RE: [PHP-DEV] PCRE jit bug with UTF-8 and lookbehind assertion
From: anatol.php@belski.net ("Anatol Belski")

Hi =C3=81ngel,

> -----Original Message-----
> From: =C3=81ngel Gonz=C3=A1lez [mailto:keisial@gmail.com]
> Sent: Thursday, February 25, 2016 9:12 PM
> To: Anatol Belski <anatol.php@belski.net>
> Cc: 'Christian Schneider' <cschneid@cschneid.com>; 'PHP internals'
> <internals@lists.php.net>
> Subject: Re: [PHP-DEV] PCRE jit bug with UTF-8 and lookbehind =
assertion
>=20
> On 21/02/16 11:42, Anatol Belski wrote:
> > Were you putting the snippets into a file or testing on the console? =
I
> > had an issue while testing this on the console, that some chars was
> > partially swallowed by terminal (which was a utf-8 terminal). When
> > putting into a file, the output is same for both - "x=C2=B0z". =
Please see
> > also the continued discussion in the original ticket
> > https://bugs.exim.org/show_bug.cgi?id=3D1189 . The offsets delivered =
by
> > PCRE also seem to be correct, and valgrind doesn't find anything. It
> > were great if you could confirm these insights. Thanks Anatol
> I was testing on a console and piping into hexdump. Using files showed =
-as
> expected- the same failure.
> The pcre-8.39 trunk (r1635), once you enable all the required options, =
does fix
> both the C test case and the php one (loading the new dynamic library =
instead of
> the system one).
>=20
> So yes, seems fixed in libpcre :)
Thanks for the further check. Yeah, 8.39 looks to be fixing the issue, =
just waiting for it to be released to upgrade in 7.0.

Regards

Anatol