Arch Linux

Description:

After an upgrade to uwsgi-plugin-php 2.0.14-2, uWSGI returns segmentation faults for all my uWSGI apps with the following output:

# /usr/bin/uwsgi --ini /etc/uwsgi/my_app.ini
[uWSGI] getting INI configuration from /etc/uwsgi/my_app.ini
*** Starting uWSGI 2.0.14 (64bit) on [Mon Jan 9 11:07:35 2017] ***
compiled with version: 6.2.1 20160830 on 26 December 2016 01:49:45
os: Linux-4.8.13-1-ARCH #1 SMP PREEMPT Fri Dec 9 07:24:34 CET 2016
nodename: my_host
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 4
current working directory: /usr/lib/systemd/system
detected binary path: /usr/bin/uwsgi
setgid() to 33
set additional group 995 (redis)
setuid() to 33
chdir() to /srv/my_app/
your processes number limit is 31643
your memory page size is 4096 bytes
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /run/uwsgi/my_app.sock fd 3
!!! uWSGI process 9982 got Segmentation Fault !!!
*** backtrace of 9982 ***
/usr/bin/uwsgi(uwsgi_backtrace+0x2c) [0x466eec]
/usr/bin/uwsgi(uwsgi_segfault+0x21) [0x4672b1]
/usr/lib/libc.so.6(+0x330b0) [0x7fe68f6280b0]
/usr/lib/uwsgi/php_plugin.so(+0x53ca) [0x7fe68de3a3ca]
*** end of backtrace ***

In seeing that php_plugin.so was the culprit of this issue, I tried downgrading to 2.0.14-1, and all my apps start normally again.

Steps to reproduce:

1. Upgrade to uwsgi-plugin-php 2.0.14-2.
2. Attempt to run a uWSGI application.