> > 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 <bis...@php.net> wrote: > On Tue, Jan 28, 2020 at 11:28 AM Benjamin Morel <benjamin.mo...@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.). >
