The following bug requires your FEEDBACK.
======================================================================
http://bugs.xdebug.org/bug_view_page.php?bug_id=0000157
======================================================================
Reporter: selkirk
Handler:
======================================================================
Project: Xdebug
Bug ID: 157
Category: Usage problems
Reproducibility: random
Severity: major
Priority: normal
Status: feedback
Operating System: Mac OS X 10.3.9
PHP Version: 5.0.4
Xdebug Version: 2.0.0beta5-dev
======================================================================
Date Submitted: 2005-10-18 16:40 CEST
Last Modified: 2005-12-30 14:40 CET
======================================================================
Summary: Consistent Random Memory Corruption
Description:
I'm experiencing fairly consistent memory corruption problems while
collecting code coverage information for a large test suite (covering
hundreds of files). These show up as odd PHP errors and failing test
cases that occur only with XDebug loaded. I have not yet been able to
complete a run of the whole test suite without encountering one of these
errors. The test suite runs fine when XDebug is not loaded.
======================================================================
----------------------------------------------------------------------
derick - 2005-10-19 10:18 CEST
----------------------------------------------------------------------
Can you please try the latest beta (2.0.0beta4) if you didn't do that yet,
and update the bugreport with the new Xdebug version filled in correctly?
If you already did that I really need a short reproducable script, or a
valgrind trace in order to figure out what is going wrong. We found no
problems here utilizing codecoverage with a huge PHPUnit2 run f.e. (but
that's with PHP 5.1.0rc3)
----------------------------------------------------------------------
selkirk - 2005-10-19 16:40 CEST
----------------------------------------------------------------------
The latest version listed on the web site is 2.0.0beta2, so I assume that
beta4 is the cvs version? I will re-try with the cvs version. Yesterday,
I noticed a spurious test failure during a regular test run with xdebug
loaded but coverage not enabled. Running a second time produced correct
results. So, I don't think the problem is not limited to just during
coverage reports.
----------------------------------------------------------------------
selkirk - 2005-10-21 01:37 CEST
----------------------------------------------------------------------
I checked out the latest version from CVS. How do I create ./configure?
It might be helpful to mention that under the "Compiling from Source"
section on http://xdebug.org/install.php
Thanks
----------------------------------------------------------------------
selkirk - 2005-10-21 01:40 CEST
----------------------------------------------------------------------
Ok, my bad. Forgot the phpize step. I never knew what that did. Now I
do. :)
----------------------------------------------------------------------
derick - 2005-12-30 14:40 CET
----------------------------------------------------------------------
Is the issue solved now?
Bug History
Date Modified Username Field Change
======================================================================
2005-10-18 16:40selkirk New Bug
2005-10-18 16:40selkirk Bug Monitored: selkirk
2005-10-19 10:18derick Bugnote Added: 0000298
2005-10-19 16:40selkirk Bugnote Added: 0000300
2005-10-21 01:37selkirk Bugnote Added: 0000302
2005-10-21 01:40selkirk Bugnote Added: 0000303
2005-12-30 14:40derick Bugnote Added: 0000317
2005-12-30 14:40derick Xdebug Version 2.0.0beta2 => 2.0.0beta5-dev
2005-12-30 14:40derick Status new => feedback
======================================================================
Received on Fri Dec 30 2005 - 14:40:25 GMT
This archive was generated by hypermail 2.2.0 : Sun Jun 24 2018 - 04:00:03 BST