Bug #18564 Updated: PHP 4.2.1+ hangs on certain pages
| From: | james at stealthnet dot co dot uk | Date: | Fri, 26 Jul 2002 11:20:29 +0000 |
| Subject: | Bug #18564 Updated: PHP 4.2.1+ hangs on certain pages | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-15325@lists.php.net to get a copy of this message | ||
ID: 18564
Updated by: james@stealthnet.co.uk
Reported By: james@stealthnet.co.uk
-Status: Feedback
+Status: Open
Bug Type: Reproducible crash
Operating System: FreeBSD 4.5
PHP Version: 4.2.2
New Comment:
GDB says:
Reading symbols from /usr/libexec/ld-elf.so.1...done.
#0 0x80d63d4 in _efree (ptr=0x829e024,
__zend_filename=0x812ff7c "zend_execute_API.c", __zend_lineno=274,
__zend_orig_filename=0x8130813 "zend_variables.c",
__zend_orig_lineno=44)
at zend_alloc.c:240
240 REMOVE_POINTER_FROM_LIST(p);
(gdb) bt
#0 0x80d63d4 in _efree (ptr=0x829e024,
__zend_filename=0x812ff7c "zend_execute_API.c", __zend_lineno=274,
__zend_orig_filename=0x8130813 "zend_variables.c",
__zend_orig_lineno=44)
at zend_alloc.c:240
#1 0x80e60d0 in _zval_dtor (zvalue=0x819a5e4,
__zend_filename=0x812ff7c "zend_execute_API.c", __zend_lineno=274)
at zend_variables.c:44
#2 0x80ddb77 in _zval_ptr_dtor (zval_ptr=0x818a430,
__zend_filename=0x8130813 "zend_variables.c", __zend_lineno=189)
at zend_execute_API.c:274
#3 0x80e6488 in _zval_ptr_dtor_wrapper (zval_ptr=0x818a430)
at zend_variables.c:189
#4 0x80ecb8a in zend_hash_destroy (ht=0x8158de8) at zend_hash.c:541
#5 0x80dd876 in shutdown_executor () at zend_execute_API.c:173
#6 0x80e72c4 in zend_deactivate () at zend.c:596
#7 0x805cc72 in php_request_shutdown (dummy=0x0) at main.c:787
#8 0x805b582 in main (argc=3, argv=0xbfbffbd8) at cgi_main.c:827
#9 0x805a565 in _start ()
Note no execute() function which seems to tie in with my not always
finding connection attempts logged in the f4p.log access log (well,
clutching at straws).
Previous Comments:
------------------------------------------------------------------------
[2002-07-26 06:10:07] killswitch@hackermail.com
I have a similar problem. After a system crash I couldnt access my
website anymore. I used lynx to connect to my site and it hangs
displaying this message: HTTP request sent; waiting for response. I
tried to access to a subdirectory and my PHP pages are displayed
correctly. (All pages are accessing the same mysql database). I tried
an other subdirectory and the browser hangs again. This was Linux Suse
7.2 (2.4.4) with preinstalled Apache and mod_php4.0.6. I thought I
could solve the problem by updating apache to 1.3.26 and PHP to 4.2.2.
The problem is still the same.
Apache doesnt recognize any connect attempts, because no log file
(error.log, access.log) contains any information about my connect
attempts to non-working PHP pages.
I created a PHP file containing <? phpinfo() ?> and put it into the
non working web root directory. This file is displayed correctly. I
tried the same with a more complex PHP file not accessing a mysql
database. It worked. How is it possible that all PHP files of a whole
directory accessing mysql databases are working and the same! files
(copy, paste) in the next directory arent?
see it in action:
www.c-f-s.de/community/ //isn't working
www.c-f-s.de/board/ //is working
------------------------------------------------------------------------
[2002-07-26 05:40:17] james@stealthnet.co.uk
Got it to crash this time:
r2b% sudo php -f xml-database.php > db.xml
php in free(): warning: recursive call
php in free(): warning: recursive call
php in free(): warning: recursive call
php in free(): warning: recursive call
php in free(): warning: recursive call
php in free(): warning: recursive call
php in free(): warning: recursive call
zsh: segmentation fault (core dumped) sudo php -f xml-database.php >
db.xml
I'm talking to people in charge to get a snapshot copy of the script
and database posted for you. FWIW I'm not using free() in my script.
------------------------------------------------------------------------
[2002-07-26 05:39:04] alan_k@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php
Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.
------------------------------------------------------------------------
[2002-07-26 05:36:01] james@stealthnet.co.uk
And now the script, that is separate to the main site that hangs,
doesn't want to segfault and instead works perfectly... For now.
To see free4phones.com hang, visit free4phones.com/home.php and hope
it's not working at the time. Apache loads mod_php4 as php was compiled
--with-apxs=/path/to/apxs.
These are some of the log messages we're getting whilst it's down:
66.185.84.74 - - [26/Jul/2002:00:04:25 +0000] "GET / HTTP/1.1" 200 5
"-" "Mozill
a/4.0 (compatible; MSIE 6.0; Windows 98)"
209.94.217.29 - - [26/Jul/2002:00:04:37 +0000] "GET / HTTP/1.1" 200 5
"-" "Mozil
la/4.0 (compatible; MSIE 5.0; Windows 98; DigExt)"
67.27.151.184 - - [26/Jul/2002:00:05:21 +0000] "GET / HTTP/1.1" 200 5
"-" "Mozil
la/4.0 (compatible; MSIE 6.0; Windows 98)"
12.2.142.7 - - [26/Jul/2002:00:05:59 +0000] "GET / HTTP/1.1" 200 5 "-"
"Mozilla/
4.0 (compatible; MSIE 5.5; Windows NT 5.0)"
216.160.234.138 - - [26/Jul/2002:00:06:59 +0000] "GET / HTTP/1.1" 200 5
"-" "Moz
illa/4.0 (compatible; MSIE 6.0; Windows 98)"
The / homepage redirects to a more suitable page (home.php) once a
country selection has been made:
r2b% grep -c home.php f4p-access.log
3
Hardly anyone has managed to get there.
------------------------------------------------------------------------
[2002-07-26 05:25:56] james@stealthnet.co.uk
With the site hung:
9:19AM up 2 days, 11:55, 1 user, load averages: 2.08, 1.99, 1.70
With the site showing a plain html page for maintenance:
9:24AM up 2 days, 12 hrs, 1 user, load averages: 0.01, 0.69, 1.17
------------------------------------------------------------------------
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/18564
--
Edit this bug report at http://bugs.php.net/?id=18564&edit=1