Bug #70398 [Asn]: SIGSEGV, Segmentation fault zend_ast_destroy_ex

From: Date: Wed, 02 Sep 2015 12:33:22 +0000
Subject: Bug #70398 [Asn]: SIGSEGV, Segmentation fault zend_ast_destroy_ex
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-195697@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=70398&edit=1 ID: 70398 Updated by: bwoebi@php.net Reported by: opitz dot alexander at googlemail dot com Summary: SIGSEGV, Segmentation fault zend_ast_destroy_ex Status: Assigned Type: Bug Package: *General Issues Operating System: Linux PHP Version: 7.0.0RC1 -Assigned To: bwoebi +Assigned To: laruence Block user comment: N Private report: N New Comment: ./sapi/cli/php -r 'define("TEST", fopen("php://temp", "w+b"));' gives me a few invalid reads with valgrind. The fix is actually simple: In shutdown_executor(), move the call to clean_non_persistent_constants(); a few lines up above zend_close_rsrc_list(&EG(regular_list)); Though, I'm not sure if that might have side-effects [AFAIK, misordering in shutdown often causes subtle breaks] … so, can you please verify, Xinchen? Previous Comments: ------------------------------------------------------------------------ [2015-09-02 09:26:12] laruence@php.net @ opitz , I asked bob to look into this one, and he already can reproduce it. but maybe fixed tomorrow. let's wait and see, thanks :) ------------------------------------------------------------------------ [2015-09-02 06:33:22] opitz dot alexander at googlemail dot com Hi laruence, is http://getcomposer.org/ or https://packagist.org/ blocked? I could provide a complete package from my master system, if this helps. ------------------------------------------------------------------------ [2015-09-02 01:49:48] laruence@php.net hmm, it's sad, composer is blocked at my country (china)... :< ------------------------------------------------------------------------ [2015-09-01 09:52:06] opitz dot alexander at googlemail dot com As the crashs are sporadic I can't provide any test script. To run TYPO3 functional tests you need to checkout TYPO3 master branch, add vendor data via composer and have a MySQL database. mkdir typo3 cd typo3 git clone git://git.typo3.org/Packages/TYPO3.CMS.git . composer.phar install To get TYPO3 ready. Running the functional tests: typo3DatabaseName="typo3_phpunit" typo3DatabaseUsername="typo3" typo3DatabasePassword="typo3typo3" typo3DatabaseHost="localhost" bin/phpunit -c typo3/sysext/core/Build/FunctionalTests.xml Please change the DB connection data to your settings. To speed up the database side of the functional tests have a look at: https://wiki.typo3.org/Functional_testing#Using_a_ram_disk_for_the_database ------------------------------------------------------------------------ [2015-09-01 09:36:53] laruence@php.net Thank you for this bug report. To properly diagnose the problem, we need a short but complete example script to be able to reproduce this bug ourselves. A proper reproducing script starts with <?php and ends with ?>, is max. 10-20 lines long and does not require any external resources such as databases, etc. If the script requires a database to demonstrate the issue, please make sure it creates all necessary tables, stored procedures etc. Please avoid embedding huge scripts into the report. or an way to reproduce it with TYPO3(reproduce instructions) ------------------------------------------------------------------------ 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=70398 -- Edit this bug report at https://bugs.php.net/bug.php?id=70398&edit=1

« previous php.bugs (#195697) next »