#25738 [Fbk]: Long Scripts Consistently Segfault
| From: | moriyoshi@php.net | Date: | Fri, 03 Oct 2003 19:46:30 +0000 |
| Subject: | #25738 [Fbk]: Long Scripts Consistently Segfault | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-48516@lists.php.net to get a copy of this message | ||
ID: 25738
Updated by: moriyoshi@php.net
Reported By: ohornoiu at bellevuechristian dot org
Status: Feedback
Bug Type: Scripting Engine problem
Operating System: Mac OS X 10.2.6+
PHP Version: 4.3.3
New Comment:
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.
NOTE: See also bug #22231, bug #22367, and bug #22510.
Previous Comments:
------------------------------------------------------------------------
[2003-10-03 15:42:10] mark dot meredith at shaw dot ca
I downloaded and compiled again. And, yes, it still
crashes. So why did my first comment on this, along with
many
others from other users on this page, as well as the #25394
page get deleted? I do not mean the comments that said "Me
too!" on OPEN bug pages. Those can go. I am referring to
the troubled user's posts that were requesting the bug be
reopened, and my feedback on the snapshots. Are those
deleted automatically? Feel free to delete this part of the
comment, just
please do not
let it go unanswered.
Thanks.
------------------------------------------------------------------------
[2003-10-03 01:53:58] sniper@php.net
Please try using this CVS snapshot:
http://snaps.php.net/php4-STABLE-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php4-win32-STABLE-latest.zip
------------------------------------------------------------------------
[2003-10-02 22:13:09] ohornoiu at bellevuechristian dot org
Description:
------------
This bug is a reference to Bug #25394 which was deemed
"bogus" without any serious research by the developers.
This is a very serious bug which basically results in the
inability to create rich, meaningful applications on OS X
since php consistently and mindlessly crashes on this
platform. The venom with which this topic was approached
by the developers in this forum in the past is entirely
innapropriate for an open source project and I expect a
more fair and thorough investigation this time since I am
providing a concrete script that is part of a huge 77,000
line project for school calendaring called Kronophobia.
I am the lead developer of this project and some of my
users have requested to run this project on Mac OS X only
to find out that this bug affects them in such a way as to
make using the program impossible. This bug does not
exist in Linux, FreeBSD or OpenBSD, all of which have been
thoroughly tested and we support.
If the php developers refuse to look at this code for some
reason because it is "beneath" them to fix a Mac problem
since they do not care about Mac OS X then I would at
least expect some sort of public statement about this and
an explanation to the Mac community of why they are to be
ostracized.
Reproduce code:
---------------
The Kronophobia package is available from the following url:
http://kronophobia.sourceforge.net
The main file of the project, index.php is the affected file as it
spans roughly 7,000 lines of code.
Expected result:
----------------
When run on any other platform besides Mac OS X, the code
renders the page in question flawlessly. The page is just
a series of switch() statements with multiple includes for
each case.
Actual result:
--------------
The actual result is an apache segfault, a "Page not
Found" error results in the browser and a crash is logged
in apache logfiles.
NO, increasing the memory limit in PHP does NOT fix this
problem like some have suggested and PHP seems to only use
about 1 megabyte of memory even after 7k lines of code.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=25738&edit=1