ID: 35147 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Closed Bug Type: Scripting Engine problem Operating System: * PHP Version: 5CVS-2005-11-08 (CVS) Assigned To: dmitry New Comment:
Fixed in CVS PHP_5_1. Previous Comments: ------------------------------------------------------------------------ [2005-11-15 14:49:44] [EMAIL PROTECTED] This bug has been fixed in CVS. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. ------------------------------------------------------------------------ [2005-11-13 20:08:37] [EMAIL PROTECTED] Proposed patches: - Against HEAD: http://www.voltex.jp/patches/php-bug-35147-preliminary.patch.diff.gz - Against PHP_5_1: http://www.voltex.jp/patches/php-bug-35147-preliminary.PHP_5_1.patch.diff.gz ------------------------------------------------------------------------ [2005-11-09 09:41:03] [EMAIL PROTECTED] Would be good to have a short reproduce script, as I can't see any problems here. ------------------------------------------------------------------------ [2005-11-08 23:38:57] [EMAIL PROTECTED] Making this critical, it really needs to be dealt with before 5.1 is released. ------------------------------------------------------------------------ [2005-11-08 05:11:21] [EMAIL PROTECTED] more details: "make install-pear" uses install-pear-nozlib.phar, which uses __HALT_COMPILER__ to prevent parsing of the rest of the file, as this would result in redeclaration of class fatal errors (it contains internal .tars for the PEAR package, but uses its own PEAR to install these .tars). When stepping through the invocation make install-pear does (sapi/cli/php -n -dshort_open_tag=0 -dsafe_mode=0 -derror_reporting=E_ALL pear/install-pear-nozlib.phar -d "/usr/local/lib/php" -b "/usr/local/bin") in gdb, it appears that zend_language_parser goes straight to an abort after the first return from the language_scanner, as if the scanner was unable to find any tokens. I was unable to run through valgrind, all available memory was used up and the process was killed before any leaks were displayed. ------------------------------------------------------------------------ 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/35147 -- Edit this bug report at http://bugs.php.net/?id=35147&edit=1
