Bug #81006 [Opn]: Segmentation fault 11 on OSX 11

From: Date: Mon, 03 May 2021 12:20:39 +0000
Subject: Bug #81006 [Opn]: Segmentation fault 11 on OSX 11
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-233658@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=81006&edit=1 ID: 81006 Updated by: nikic@php.net Reported by: sulcmil at gmail dot com Summary: Segmentation fault 11 on OSX 11 Status: Open Type: Bug Package: *General Issues Operating System: OSX 11.3 PHP Version: 8.0.5 Block user comment: N Private report: N New Comment: Yes, the change has already been reverted from both 7.4 and 8.0, though it's still a while until the next releases are planned. The change has also been reverted from ondrej/php just now (see https://github.com/oerdnj/deb.sury.org/issues/1598), so you may be able to fetch a fixed version from there soon. Previous Comments: ------------------------------------------------------------------------ [2021-05-03 11:23:05] mark dot roeling at cordeo dot com Yes, postgres and Doctrine here as well. Links point to probably related issue: https://bugs.php.net/bug.php?id=81002 Seems that the change in pdo_pgsql will be reverted in upcoming 8.0.6 version. ------------------------------------------------------------------------ [2021-05-03 10:57:55] nikic@php.net Specifically, the strol in the backtrace makes me think that this may be caused by https://github.com/php/php-src/pull/6801. The involvement of Doctrine also points to something database related. Due to the referenced change, binding a null value with PDO::PARAM_INT using PDO PgSql can lead to a segfault. ------------------------------------------------------------------------ [2021-05-03 10:56:42] sulcmil at gmail dot com Yes, I use Postgres. ------------------------------------------------------------------------ [2021-05-03 10:52:38] nikic@php.net Do you use postgres? ------------------------------------------------------------------------ [2021-05-03 10:51:29] mark dot roeling at cordeo dot com (since the voting seems to have a bug as well) Yes, encountering same/similar issue since upgrade to php8.0.5 this morning, on Ubuntu 18.04.5 using ppa:ondrej/php for php and nginx. I tried to use apport-retrace to retrieve additional information: Reading symbols from /usr/sbin/php-fpm8.0...(no debugging symbols found)...done. [New LWP 17091] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `php-fpm: pool www '. Program terminated with signal SIGSEGV, Segmentation fault. #0 __GI_____strtol_l_internal (nptr=0x18 <error: Cannot access memory at address 0x18>, endptr=0x0, base=10, group=<optimized out>, loc=0x7f975972a560 <_nl_global_locale>) at ../stdlib/strtol_l.c:292 292 ../stdlib/strtol_l.c: Bestand of map bestaat niet. (last line translates to: File or folder doesn't exist) Similar errors occur on MacOS and Ubuntu server (18.04.5) as well. [03-May-2021 12:07:55] WARNING: [pool **EDITED-appname**] child 99 exited on signal 11 (SIGSEGV) after 671.400078 seconds from start ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=81006 -- Edit this bug report at https://bugs.php.net/bug.php?id=81006&edit=1

« previous php.bugs (#233658) next »