Bug #79395 [Fbk->Opn]: SIGABRT from child when accessing website

From: Date: Mon, 23 Mar 2020 11:33:59 +0000
Subject: Bug #79395 [Fbk->Opn]: SIGABRT from child when accessing website
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-226232@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=79395&edit=1 ID: 79395 User updated by: antony dot landsman at verticacrm dot com Reported by: antony dot landsman at verticacrm dot com Summary: SIGABRT from child when accessing website -Status: Feedback +Status: Open Type: Bug Package: FPM related Operating System: Centos 8.1.1911 (Core) PHP Version: 7.3.15 Block user comment: N Private report: N New Comment: This only occurs when xdebug is enabled. As an eexample the following script:- <?php ob_start(); $result = eval("?>".$string."<"."?p"."hp return 1;"); $new_string = ob_get_clean(); s What I expect is an undefined variable string error message When I disable xdebug that is exactly what I get in the log:- 2020/03/23 11:26:46 [error] 30332#30332: *3115 FastCGI sent in stderr: "PHP message: PHP Notice: Undefined variable: string in /home/brgb/public_html/crm/pinf.php on line 3" while reading response header from upstream, client: 82.80.188.85, server: crm.brgbrokers.com, request: "GET /pinf.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php7-brgb-fpm.sock:", host: "crm.brgbrokers.com" if however I enable xdebug in my php.ini, In the server error log I get a connection reset by peer error message, and the the php error log I get child 7584 exited on signal 6 (SIGABRT) after 960.531820 seconds from start while I originally reported this on centos 8 and php 7.3.15 I have also experienced the same with centos 7 and php 7.3.16 Previous Comments: ------------------------------------------------------------------------ [2020-03-18 14:53:27] requinix@php.net Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.php.net/how-to-report.php If you can provide more information, feel free to add it to this bug and change the status back to "Open". Thank you for your interest in PHP. You can still get a stack trace with a release build, but it won't be as useful. Try with all modules and zend_modules disabled? How about 7.3.16, which was tagged yesterday and will be announced tomorrow? ------------------------------------------------------------------------ [2020-03-18 14:42:53] antony dot landsman at verticacrm dot com Description: ------------ I recently built a copy of 7.3.15. When I try to access my website (running on NGINX) I get a 502 error. In looking at the logs I see that the child process is terminating with a SIGABRT (Signal 6). In order to gather more information, I created a debug build. To my surprise, with the debug build the site works perfectly. Sort of a catch 22, because as IU understand it, I cannot get a stack trace without a debug build. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=79395&edit=1

« previous php.bugs (#226232) next »