Bug #51216 [Com]: Segmentation fault when compiling PHP with PHAR

Edit report at http://bugs.php.net/bug.php?id=51216&edit=1

 ID:               51216
 Comment by:       mm_half3 at yahoo dot com
 Reported by:      dtm2mcs at gmail dot com
 Summary:          Segmentation fault when compiling PHP with PHAR
 Status:           Open
 Type:             Bug
 Package:          PHAR related
 Operating System: Ubuntu 6.04 + CentOS 5.4
 PHP Version:      5.3.2

 New Comment:

For what it is worth, I had the same issue on Solaris 10 sparc,
compiling with gcc-4.3.1, and php-5.32 (tried with stable release and
latest development src).   Further research found other solaris types
getting segmentation faults during php 5.2.xx make test, see
http://bugs.php.net/bug.php?id=47824&edit=1 .  Which I also could
reproduce.  Setting CFLAGS=-O1, got php5.32 to compile and make test
successfully with phar, and 5.2.xx to compile without fatal errors.  The
seg fault is probably not a php issue, but something in the gcc version.
 The make test looks like all the tests run, but there is an issue when
the Test Summary is done for both:

WARNED TEST SUMMARY
---------------------------------------------------------------------
via [ext/pdo_sqlite/tests/common.phpt]
        SQLite PDO Common: Bug #34630 (inserting streams as LOBs)
[ext/pdo_sqlite/tests/bug_34630.phpt] (warn: XFAIL section but test
passes)
via [ext/sqlite/tests/pdo/common.phpt]
        SQLite2 PDO Common: Bug #34630 (inserting streams as LOBs)
[ext/sqlite/tests/pdo/bug_34630.phpt] (warn: XFAIL section but test
passes)
=====================================================================

You may have found a problem in PHP.
We would like to send this report automatically to the
PHP QA team, to give us a better understanding of how
the test cases are doing. If you don't want to send it
immediately, you can choose "s" to save the report to
a file that you can send us later.
Do you want to send this report now? [Yns]: s
Please send /tmp/php-5.3.2/php_test_results_20100325_2040.txt to
[email protected] manually, thank you.


Previous Comments:
------------------------------------------------------------------------
[2010-03-24 17:51:27] paul at boxuk dot com

i can also reproduce this, i believe it's something to do with the fix
for bug 
#50829

amended that bug with the details

------------------------------------------------------------------------
[2010-03-22 11:32:02] creatorbri at gmail dot com

I have the same problem when attempting to compile PHP 5.3.2. Details:

PHP Version:
PHP 5.3.2 - I downloaded the "stable" release dated "04 Mar 2010"
directly from 
one of the usual php.net mirrors

Platform:
Ubuntu 9.10 Karmic Koala x64
[Asus G60Jx-RBBx05 - Core i5-430 2.26 GHz 4.0 GB RAM]

Configure Options:
./configure --prefix=PREFIX --with-apxs2=/usr/bin/apxs2
--with-mysql=/usr --
with-mysqli=/usr/bin/mysql_config --with-pgsql=/usr --with-tidy=/usr
--with-
curl=/usr/bin --with-curlwrappers --with-openssl-dir=/usr
--with-zlib-dir=/usr -
-enable-mbstring --with-xpm-dir=/usr --with-pdo-pgsql=/usr
--with-pdo-mysql=/usr 
--with-xsl=/usr --with-ldap --with-xmlrpc --with-iconv-dir=/usr
--with-snmp=/usr 
--enable-exif --enable-calendar --with-bz2=/usr --with-mcrypt=/usr
--with-gd --
with-jpeg-dir=/usr --with-png-dir=/usr --with-zlib-dir=/usr
--with-freetype-
dir=/usr --enable-mbstring --enable-zip --with-pear

ERROR:
ext/sqlite3/libsqlite/.libs/sqlite3.o: In function `memset':
/usr/include/bits/string3.h:82: warning: memset used with constant zero
length 
parameter; this could be due to transposed parameters
Generating phar.php
Segmentation fault
make: *** [ext/phar/phar.php] Error 139

------------------------------------------------------------------------
[2010-03-16 16:22:12] vnegrier at optilian dot com

Not PHAR related, this is actually the php-cli binary segfaulting during
the make process.

Here is a trace :

0x0839c8f4 in zend_startup_module_ex (module=0x8732210,
tsrm_ls=0x8712070)
    at /usr/src/php-5.3.2/Zend/zend_API.c:1618
1618                    EG(current_module) = NULL;
(gdb) where
#0  0x0839c8f4 in zend_startup_module_ex (module=0x8732210,
tsrm_ls=0x8712070)
    at /usr/src/php-5.3.2/Zend/zend_API.c:1618
#1  0x083a177a in zend_hash_apply (ht=0x8711460,
    apply_func=0x839c850 <zend_startup_module_ex>, tsrm_ls=0x8712070)
    at /usr/src/php-5.3.2/Zend/zend_hash.c:673
#2  0x0839c75a in zend_startup_modules (tsrm_ls=0x8712070)
    at /usr/src/php-5.3.2/Zend/zend_API.c:1662
#3  0x083372f0 in php_module_startup (sf=0x86f82c0,
additional_modules=0x0,
    num_additional_modules=0) at /usr/src/php-5.3.2/main/main.c:2022
#4  0x084299f1 in php_cli_startup (sapi_module=0x86f82c0)
    at /usr/src/php-5.3.2/sapi/cli/php_cli.c:401
#5  0x0842a32c in main (argc=1, argv=0xbfffcf74)
    at /usr/src/php-5.3.2/sapi/cli/php_cli.c:775

This was reproduced on debian 5.0.4 x86

------------------------------------------------------------------------
[2010-03-12 11:39:22] jedibc at free dot fr

Same issue on debian lenny x86 :

Generating phar.php
/bin/sh: line 1: 16624 Segmentation fault      ` if test -x
"/root/php-5.3.2/sapi/cli/php"; then /root/php-5.3.2/build/shtool echo
-n -- "/root/php-5.3.2/sapi/cli/php -n"; if test "x" != "x"; then
/root/php-5.3.2/build/shtool echo -n -- " -d
extension_dir=/root/php-5.3.2/modules"; for i in bz2 zlib phar; do if
test -f "/root/php-5.3.2/modules/$i.la"; then .
/root/php-5.3.2/modules/$i.la; /root/php-5.3.2/build/shtool echo -n -- "
-d extension=$dlname"; fi; done; fi; else /root/php-5.3.2/build/shtool
echo -n -- "/root/php-5.3.2/sapi/cli/php"; fi;` -d 'open_basedir=' -d
'output_buffering=0' -d 'memory_limit=-1' -d phar.readonly=0 -d
'safe_mode=0' /root/php-5.3.2/ext/phar/build_precommand.php >
ext/phar/phar.php

make: *** [ext/phar/phar.php] Error 139

------------------------------------------------------------------------
[2010-03-10 12:38:52] fsk141 at gmail dot com

I'm having the same issue trying to compile on Arch Linux on the ARM
platform... :(

make: *** [ext/phar/phar.php] Error 139

------------------------------------------------------------------------


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

    http://bugs.php.net/bug.php?id=51216


-- 
Edit this bug report at http://bugs.php.net/bug.php?id=51216&edit=1