Edit report at https://bugs.php.net/bug.php?id=71659&edit=1
ID: 71659
Comment by: inefedor at gmail dot com
Reported by: nish dot aravamudan at canonical dot com
Summary: segmentation fault in pcre running twig tests
Status: Open
Type: Bug
Package: Reproducible crash
Operating System: Ubuntu 16.04
PHP Version: 7.0.3
Block user comment: N
Private report: N
New Comment:
Probably when phpunit runs tests in different process, it uses another php binary or another set of
php.ini settings.
Previous Comments:
------------------------------------------------------------------------
[2016-03-02 16:45:14] nish dot aravamudan at canonical dot com
https://bugs.exim.org/show_bug.cgi?id=1803
filed.
However, two updates from my testing last night.
1) The twig testsuite is run using phpunit. phpunit has a parameter --process-isolation. When the
tests are run with that parameter, the tests pass (even with pcre.jit left on). This, I think,
points to a PHP bug, but I'm not sure.
2) When I tried to just run the failing twig tests on their own (split_utf8.test and
length_utf8.test are the two input files), I could not recreate the segmentation fault. This again,
it feels like, points to a fault somewhere in the php logic due to some corrupt state, perhaps?
------------------------------------------------------------------------
[2016-02-28 08:38:43] pajoye@php.net
One of the JIT bugs in pcre. It should be reported upstream.
------------------------------------------------------------------------
[2016-02-26 21:34:38] nish dot aravamudan at canonical dot com
Adding pcre.jit=0 to the invocation of the tests (-d parameter to phpunit) allows the test to
succeed.
------------------------------------------------------------------------
[2016-02-26 02:41:08] nish dot aravamudan at canonical dot com
I apologize, but I'm not a PHP developer. The twig testsuite is publicly available from github.
------------------------------------------------------------------------
[2016-02-25 07:24:21] laruence@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.
A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external
resources such as databases, etc. If the script requires a
database to demonstrate the issue, please make sure it creates
all necessary tables, stored procedures etc.
Please avoid embedding huge scripts into the report.
------------------------------------------------------------------------
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=71659
--
Edit this bug report at https://bugs.php.net/bug.php?id=71659&edit=1