Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108325
MIME-Version: 1.0
References: <CAG9XoMTnmK=+7h2D1YchjpPcCfzrUVrouS_Vf84XQ3ajnLCzNA@mail.gmail.com>
 <CAEYWF=5V2j+mhaLZRyk6vDz6joPX=uNMpYE9BJhLWZgSn8M_Ew@mail.gmail.com>
In-Reply-To: <CAEYWF=5V2j+mhaLZRyk6vDz6joPX=uNMpYE9BJhLWZgSn8M_Ew@mail.gmail.com>
Date: Wed, 29 Jan 2020 23:58:41 +0100
Message-ID: <CAG9XoMQ_fRm+qfsoA9C+OAhEdx-qJna3d+DvYxoU075UJgunXQ@mail.gmail.com>
To: bishop@php.net
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000cead52059d4f488f"
Subject: Re: [PHP-DEV] How to debug a segmentation fault?
From: benjamin.morel@gmail.com (Benjamin Morel)

--000000000000cead52059d4f488f
Content-Type: text/plain; charset="UTF-8"

>
> I would add, since you're using PHP-FPM, that the pool configuration needs
> to have:
> process.dumpable = 1


Thank you! I could not generate a core dump before adding this
configuration option!
The generating a gdb backtrace
<https://bugs.php.net/bugs-generating-backtrace.php> page looks a big
outdated, it would be nice if someone could update it will all the helpful
info received in this thread.

I'm not sure if I could gather helpful enough info about the issue, but
anyway I filed a bug here:
https://bugs.php.net/bug.php?id=79194

Thank you,
Benjamin

On Wed, 29 Jan 2020 at 18:19, Bishop Bettini <bishop@php.net> wrote:

> 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.).
>

--000000000000cead52059d4f488f--