ID:               50382
 Updated by:       j...@php.net
 Reported By:      dirk at bean-it dot nl
-Status:           Open
+Status:           Assigned
 Bug Type:         Reproducible crash
 Operating System: Debian 5.0
 PHP Version:      5.3.1
-Assigned To:      
+Assigned To:      dmitry


Previous Comments:
------------------------------------------------------------------------

[2009-12-07 08:43:02] dirk at bean-it dot nl

I can confirm that setting: zend.enable_gc=Off makes the crash go
away.

I'm still looking to pinpoint the problem. I hope I can provide a short
script which crashes php.

------------------------------------------------------------------------

[2009-12-06 15:23:28] srina...@php.net

alternatively, you can also set "zend.enable_gc=Off" within your
php.ini 
and this should make the crash go away as well. 

------------------------------------------------------------------------

[2009-12-05 16:14:38] srina...@php.net


from the bt, I guess, there is memory corruption within Zend engine.

if you are able to reproduce this crash by running a modified version
of 
your script from the command line, then , to help us more understand
the 
problem, will it be possible for you to run it with valgrind --num-
callers=15 --error-limit=no  ./sapi/cli/php <test-script>

alternatively, if you export USE_ZEND_ALLOC=0 in your apachectl script,

your server might run successfully albeit at decreased performance. 

thanks for your help



------------------------------------------------------------------------

[2009-12-04 12:56:47] dirk at bean-it dot nl

Up till now, I haven't been able to exactly pinpoint the problem. As
mentioned below, our application works as expected, it looks likes
Apache crashes -after- php has compiled the page. Very strange. The
application is quite large, a lot of code. Tried to debug with Zend
Debugger, but than things work as expected, no segfault.

As much as I would like to give some example code, I cannot at this
moment, since I have no clue where things go wrong (the app works
fine!). 

Any suggestions on how to proceed are highly appreciated.

------------------------------------------------------------------------

[2009-12-04 12:39:33] j...@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 the script requires a 
database to demonstrate the issue, please make sure it creates 
all necessary tables, stored procedures etc.

Please avoid embedding huge scripts into the report.



------------------------------------------------------------------------

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/50382

-- 
Edit this bug report at http://bugs.php.net/?id=50382&edit=1

Reply via email to