#31119 [Fbk->NoF]: php crashes apache2 child and in interactive mode

From: Date: Wed, 09 Feb 2005 00:00:20 +0000
Subject: #31119 [Fbk->NoF]: php crashes apache2 child and in interactive mode
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-73679@lists.php.net to get a copy of this message
ID: 31119 Updated by: php-bugs@lists.php.net Reported By: shoorik at ilyichevsk dot net -Status: Feedback +Status: No Feedback Bug Type: Scripting Engine problem Operating System: * (ZTS only!) PHP Version: 4.3.10, 5.0.3 New Comment: No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". Previous Comments: ------------------------------------------------------------------------ [2005-02-01 19:12:33] sniper@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 possible, make the script source available online and provide an URL to it here. Try to avoid embedding huge scripts into the report. ------------------------------------------------------------------------ [2005-01-18 09:16:00] shoorik at ilyichevsk dot net Well, as I could figure out PHP crashes while processing phpMyAdmin lang/english-iso-8859-1.inc.php - there is just defined big amount ov variables and nothing like "ugly code"... As I wrote above - I could not repeat this bug anywhere else - all other sites works fine. ------------------------------------------------------------------------ [2004-12-16 15:41:39] shoorik at ilyichevsk dot net In addition. 5.0.3 has the same behaviour. Crash in interactive mode and web requests on phpMyAdmin/index.php What is interesting - with almost sam backtrace... Program received signal SIGSEGV, Segmentation fault. 0x081b74a3 in execute (op_array=0x83af30c, tsrm_ls=0x821a1f0) at /usr/local/src/php-5.0.3/Zend/zend_execute.c:1400 1400 if (EX(opline)->handler(&execute_data, EX(opline), op_array TSRMLS_CC)) { (gdb) bt #0 0x081b74a3 in execute (op_array=0x83af30c, tsrm_ls=0x821a1f0) at /usr/local/src/php-5.0.3/Zend/zend_execute.c:1400 #1 0x0818efaf in execute_new_code (tsrm_ls=0x821a1f0) at /usr/local/src/php-5.0.3/Zend/zend_execute_API.c:1074 #2 0x08177a9c in zendparse (tsrm_ls=0x821a1f0) at Zend/zend_language_parser.c:2359 #3 0x0817b9aa in compile_file (file_handle=0xbfbfc000, type=8, tsrm_ls=0x821a1f0) at Zend/zend_language_scanner.c:3142 #4 0x081bcfbb in zend_include_or_eval_handler (execute_data=0xbfbfc090, opline=0x831500c, op_array=0xa, tsrm_ls=0x821a1f0) at /usr/local/src/php-5.0.3/Zend/zend_execute.c:3517 #5 0x081b74a5 in execute (op_array=0x821bf0c, tsrm_ls=0x821a1f0) at /usr/local/src/php-5.0.3/Zend/zend_execute.c:1400 #6 0x0818efaf in execute_new_code (tsrm_ls=0x821a1f0) at /usr/local/src/php-5.0.3/Zend/zend_execute_API.c:1074 #7 0x08177a9c in zendparse (tsrm_ls=0x821a1f0) at Zend/zend_language_parser.c:2359 OK! I give up! Will try to figure out what call\syntax causes exactly system crash and post there if something. ------------------------------------------------------------------------ [2004-12-16 13:16:57] shoorik at ilyichevsk dot net Prefork mpm works nice, but I must solve few issues with CGI zombies using threads that way. Thats why I tried to use worker mpm. Anyway - there is few sites which still work on threaded php - I got this crash only with phpMyAdmin (still trying to find out WHERE?). So I must not use thread features anyway... Sadly... Will PHP team fix this is fuftre anyway? Perl story reproduces? ------------------------------------------------------------------------ [2004-12-16 13:04:03] sniper@php.net Does it crash if you compile Apache with prefork mpm ?? ie. don't even try to use threading with php, it doesn't work. ------------------------------------------------------------------------ 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/31119 -- Edit this bug report at http://bugs.php.net/?id=31119&edit=1

« previous php.bugs (#73679) next »