Bug #67735 [Com]: PHPNG: segfault when running "composer update"

Edit report at https://bugs.php.net/bug.php?id=67735&edit=1 ID: 67735 Comment by: ingo dot walz at googlemail dot com Reported by: pascal dot chevrel at free dot fr Summary: PHPNG: segfault when running "composer update" Status: Open Type: Bug Package: *General Issues Operating System: Linux PHP Version: Irrelevant Block user comment: N Private report: N New Comment: I got a backtrace running the composer test suite against phpng: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00000000009dbbbc in destroy_zend_class (pce=0x25c94b8) at /home/dev/phpng/php-src/Zend/zend_opcode.c:273 273 if (--ce->refcount > 0) { (gdb) bt #0 0x00000000009dbbbc in destroy_zend_class (pce=0x25c94b8) at /home/dev/phpng/php-src/Zend/zend_opcode.c:273 #1 0x0000000000a025ff in zend_hash_destroy (ht=0x22932a0) at /home/dev/phpng/php-src/Zend/zend_hash.c:548 #2 0x00000000009eb924 in compiler_globals_dtor (compiler_globals=0x2292ef0, tsrm_ls=0x228fd30) at /home/dev/phpng/php-src/Zend/zend.c:544 #3 0x0000000000926017 in tsrm_shutdown () at /home/dev/phpng/php-src/TSRM/TSRM.c:180 #4 0x0000000000ab7a6e in main (argc=4, argv=0x228fbe0) at /home/dev/phpng/php-src/sapi/cli/php_cli.c:1399 It happened with this data provider value: https://github.com/composer/composer/blob/master/tests/Composer/Test/Repository/PearRepositoryTest.php#L94-L99 Previous Comments: ------------------------------------------------------------------------ [2014-08-11 19:31:45] ingo dot walz at googlemail dot com If you can provide additional information, I can try to reproduce it and generate the backtrace. I saw a really strange behaviour in atoum, but no segfault. I tried to run the atoum testsuite with phpng, installed via composer: composer.json: { "require": { "atoum/atoum": "*" } } $ wget https://getcomposer.org/composer.phar $ ../phpng/bin/php composer.phar update $ cd vendor/atoum/atoum/ $ ../phpng/bin/php scripts/runner.php --test-it [ Skip ] Error: Data provider mageekguy\atoum\tests\units\asserters\float::testIsNearlyEqualToDataProvider() is unknown (linked to this condition https://github.com/atoum/atoum/blob/master/classes/test.php#L1310 ) The same with a regular git checkout (also with phpng): $ git clone https://github.com/atoum/atoum . $ ../phpng/bin/php scripts/runner.php --test-it -> Works fine, no Exception No errors with PHP 5.5.14 in both variants ... Following could be helpful: - The atoum testfile, causing the segfault - The version of atoum I can provide the backtrace if I'm able to reproduce it. Not sure if we're talking about the same issue ... ------------------------------------------------------------------------ [2014-08-11 14:24:18] tyrael@php.net as Julien mentioned previously here is how to generate a backtrace from a coredump: https://bugs.php.net/bugs-generating-backtrace.php basically you call gdb (which assumes you have gdb installed and it is also advised to have the debug symbols installed otherwise the backtrace won't be much help) with the binary which was used to generate the dump (the php cli in your case) and the crashdump: gdb /path/to/php /path/to/the/core/file then from gdb you execute: bt then you can copypaste the backtrace to the bugreport. ------------------------------------------------------------------------ [2014-08-11 14:10:19] imprec at gmail dot com Just copy/paste the backtrace as bug comment ------------------------------------------------------------------------ [2014-08-07 23:42:27] pascal dot chevrel at free dot fr ok, I found out that Ubuntu keeps backtraces for crashes in /var/crash, how can I provide this file to you guys? I don't see an attachment feature on the bug tracker apart from the "attach a patch" one. ------------------------------------------------------------------------ [2014-08-07 23:33:42] pascal dot chevrel at free dot fr FYI, the segfault no longer happen with the last .deb provided by Zend (PHP 5.7.0-dev (cli) (built: Aug 7 2014 16:17:33) But now the segfault happens with the use of Atoum. I looked at the doc to generate a backtrace and it looks Chinese to me, sorry :) ------------------------------------------------------------------------ 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=67735 -- Edit this bug report at https://bugs.php.net/bug.php?id=67735&edit=1