Re: PHP5.4: PHP-FPM + Gettext == invalid pointer

Hi Pierre, Sorry, I didn't know these issues had been addressed to. I just installed the latest version from trunk. Everything runs smoothly, no segfaults or dumps anymore. Thanks again, Steven On 03/23/2012 01:25 PM, Pierre Joye wrote:

yes, please do. We have fixed these errors recently. On Fri, Mar 23, 2012 at 1:13 PM, Steven VAN POECK<svanpoeck@gmail.com> wrote:

Hi Pierre, Right. Disabling apc solves the issue, with or without gettext activated. No dump or segfault message anymore. I'm using the standard APC installed by pecl install apc. Version is 3.1.9. It seems to be working fine although it's responsible for the PHP-FPM dump. Should I use the version from SVN's trunk ? Thanks, Steven On 03/23/2012 01:06 PM, Pierre Joye wrote:

hi, Please disable APC too to test. btw, do you use APC from current svn's trunk? Cheers, On Fri, Mar 23, 2012 at 12:51 PM, Steven VAN POECK<svanpoeck@gmail.com> wrote:

Hi, Whenever I activate the gettext extension, PHP-FPM dumps a heap upon starting (see output below) Although the output finishes with "Aborted. Failed", the php processes are working ok, gettext too. PHP 5.4 was compiled with these options: ./configure --sysconfdir=/etc/php5 --with-config-file-path=/etc/php5 --with-config-file-scan-dir=/etc/php5/conf.d --enable-fpm --with-fpm-user=www-data --with-fpm-group=www-data --with-openssl --with-zlib=shared --enable-bcmath --with-curl=shared --with-gd=shared --with-gettext=shared --enable-intl --enable-mbstring --with-mcrypt=shared --enable-pcntl --disable-pdo --with-mysqli=mysqlnd --disable-posix --with-libedit=shared --with-readline=shared --with-recode=shared --enable-sockets --with-tidy=shared --with-xsl=shared --enable-zip --with-pear --with-gmp=shared If I deactivate the gettext extension, PHP-FPM systematically segfaults upon startup but still runs fine: root@some-vm:~# /etc/init.d/php-fpm restart Gracefully shutting down php-fpm . done Starting php-fpm Segmentation fault failed The app is running on an nginx 0.7.67 Just wanted to know if this is normal behaviour and if not, should I file a bug ? Thanks, Steven