Bug #75669 [Com]: Segmentation Fault

From: Date: Thu, 08 Oct 2020 15:55:10 +0000
Subject: Bug #75669 [Com]: Segmentation Fault
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-229477@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=75669&edit=1 ID: 75669 Comment by: josh at servebyte dot com Reported by: humairm at gmail dot com Summary: Segmentation Fault Status: Open Type: Bug Package: MySQLi related Operating System: Linux PHP Version: 7.1.12 Block user comment: N Private report: N New Comment: I'm seeing the same issue with PHP 7.4.11, except no SIGSEGV with 7.3.23 Previous Comments: ------------------------------------------------------------------------ [2017-12-12 04:27:38] humairm at gmail dot com Description: ------------ running php 7 using php-fpm on lighttpd with mysqli on mariadb causes segmentation fault at mysqli_stmt_bind_result as reported in php-fpm.log: [pool www] child 24047 exited on signal 11 (SIGSEGV) after 6.518082 seconds from start lighttpd logs report the following error: mod_fastcgi.c.2424 unexpected end-of-file (perhaps the fastcgi process died) 2 key observations: 1. commenting out the bind_result line eliminates the error - so something triggers the segmentation fault when bind_result is called under php 7 (7.1.2) 2. running php 5 (5.5.9) instead of php 7 (7.1.2) does not have the same issue - so it seems there is something in php version 7.1.2 that is triggering the sigsegv Test script: --------------- $stmt = $db->prepare($sql); $stmt->execute(); $stmt->bind_result($id, $name); //This is where segmentation fault occurs - if this line is commented out then the error goes away but so does the logic! Same line does not cause any issue with php 5 and works as desired returning the result set successfully. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=75669&edit=1

« previous php.bugs (#229477) next »