Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108321
MIME-Version: 1.0
References: <CAG9XoMTnmK=+7h2D1YchjpPcCfzrUVrouS_Vf84XQ3ajnLCzNA@mail.gmail.com>
In-Reply-To: <CAG9XoMTnmK=+7h2D1YchjpPcCfzrUVrouS_Vf84XQ3ajnLCzNA@mail.gmail.com>
Reply-To: bishop@php.net
Date: Wed, 29 Jan 2020 12:19:16 -0500
Message-ID: <CAEYWF=5V2j+mhaLZRyk6vDz6joPX=uNMpYE9BJhLWZgSn8M_Ew@mail.gmail.com>
To: Benjamin Morel <benjamin.morel@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009cb29e059d4a8aaf"
Subject: Re: [PHP-DEV] How to debug a segmentation fault?
From: bishop@php.net (Bishop Bettini)

--0000000000009cb29e059d4a8aaf
Content-Type: text/plain; charset="UTF-8"

On Tue, Jan 28, 2020 at 11:28 AM Benjamin Morel <benjamin.morel@gmail.com>
wrote:

> I'm encountering a SIGSEGV in PHP-FPM on PHP 7.4.2 in a Symfony app. The
> bug seems to happen during the rendering of a Twig template; this makes it
> hard for me to pinpoint the code that triggers the segfault.
>
> Could you please tell me what the procedure to collect information is, so
> that I can file a useful bug report?
>

Great advice so far. I would add, since you're using PHP-FPM, that the pool
configuration needs to have:

process.dumpable = 1

to get core dumps out of workers. Without this you might not get core
dumps, even when you have other core dump settings configured (ulimit -c
unlimited, chmod +r phpfpm, etc.).

--0000000000009cb29e059d4a8aaf--