Bug #18258 Updated: Gettting frequent Seg Faults on PHP scripts
| From: | david+php dot net at blue-labs dot org | Date: | Wed, 17 Jul 2002 15:35:43 +0000 |
| Subject: | Bug #18258 Updated: Gettting frequent Seg Faults on PHP scripts | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-14417@lists.php.net to get a copy of this message | ||
ID: 18258
Updated by: david+php.net@blue-labs.org
Reported By: tauren@servlets.net
Status: Feedback
Bug Type: Reproducible crash
Operating System: Red Hat 6.2
PHP Version: 4.2.1
New Comment:
You'll have to ignore sniper@php.net, he|it|whatever seems to ask for
backtraces regardless of their already being posted.
I have a similar problem but I've narrowed it down to sessions.
<?php
session_start();
?>
This code is sufficient to cause a segfault, I just added my two cents
to another bug, I'll fetch that in a moment. Are you by chance using
sessions?
Previous Comments:
------------------------------------------------------------------------
[2002-07-12 03:56:32] alan_k@php.net
You mentioned that you do not get segfaults on the phpinfo page anymore
(which is where the last gdb back trace indicated you did).
So the last backtrace is not usefull anymore.. - can you run the site
again in gdb, apache -X etc. and try and make it segfault.
you may also like to try arvins rpms for redhat 6.2?
http://rpms.arvin.dk/php/rh62/i586/
------------------------------------------------------------------------
[2002-07-12 03:44:20] tauren@servlets.net
Hi sniper@php.net,
Thanks for the response. You asked for a backtrace in your message
even though I have already submitted several of them. Are the ones
I've submitted not useful? What more do you suggest I do?
Tauren
------------------------------------------------------------------------
[2002-07-11 22:01:24] sniper@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-11 18:24:47] tauren@servlets.net
Any ideas on what is going on here? All of my hosted sites that use
PHP have very poor performance right now because of all the seg faults.
I've tried rolling back to what was installed previously, but I'm
still getting the problem. I've tried compiling Apahce/PHP with no
additional options and features, but the problem still persists. I'm
going to try 1.3.26 with an older PHP 4.1 version next. Some messages
on Google seem to indicate that others had success by reverting back.
Any help would be much appreciated!
Tauren
------------------------------------------------------------------------
[2002-07-10 07:42:01] tauren@servlets.net
After looking around on my system, it looks like libmcrypt is fairly
old. It was installed in March 2001. So I removed it and installed
2.5.1 (it was handy -- I didn't realize 2.5.2 was out when I installed
it).
I also found that libmhash, libfreetype, libt1, and other libraries
were fairly old too. So I cleaned all of them up and installed recent
versions. I then recompiled Apache/PHP.
Unfortunately, the problem still exists with the Segmentation Faults.
However, now I can't get a backtrace in gdb because hitting the
phpinfo.php page no longer causes gdb to halt like it was before. This
is even though I'm having just as much if not more trouble bringing up
phpinfo.php now that I've reinstalled everything.
Tomorrow I think that I'll reinstall again with a very bare-bones
Apache/PHP installation and see if I still have problems. In the
meantime, if anyone has more suggestions, please let me know!
Thanks again,
Tauren
------------------------------------------------------------------------
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/18258
--
Edit this bug report at http://bugs.php.net/?id=18258&edit=1