Edit report at https://bugs.php.net/bug.php?id=53976&edit=1
ID: 53976
Comment by: rasta at lj dot sk
Reported by: matthew dot scott dot day at gmail dot com
Summary: running phpunit causes seg fault in php garbage
collection
Status: Open
Type: Bug
Package: Reproducible crash
Operating System: ubuntu 10.10
PHP Version: 5.3.5
Block user comment: N
Private report: N
New Comment:
i am having the same problem.
running phpunit -dzend.enable_gc=0 works without failure
Previous Comments:
------------------------------------------------------------------------
[2011-10-28 14:10:04] deviantintegral at gmail dot com
I'm running into this with running phpunit for symfony2 tests on Ubuntu 10.04.
If I disable garbage collection by running phpunit with "-dzend.enable_gc=0"
everything runs fine.
------------------------------------------------------------------------
[2011-08-23 07:57:23] francesco dot monte at gmail dot com
I'm expecting the same issue. Did you got what caused it?
------------------------------------------------------------------------
[2011-07-24 18:32:28] zhengxiang dot pan at alcatel-lucent dot com
I observed this program too.
mongodb PHP driver unit test testEnsureUniqueIndex in MongoCollectionTest.php
can reproduce this program. I run php 5.3.6 on Ubuntu.
------------------------------------------------------------------------
[2011-02-13 04:38:00] [email protected]
This is nigh-impossible to debug without a reproducing script; the stack trace
is the most generic crash on shutdown you can get. The fact the crash doesn't
happen on xdebug code doesn't mean it wasn't xdebug that corrupted the state
and ultimately caused the crash on shutdown.
------------------------------------------------------------------------
[2011-02-11 23:19:23] matthew dot scott dot day at gmail dot com
you can't run phpunit with code coverage without xdebug. i already posted this
to the xdebug bug tracker and he said it's php garbage collection that's
causing the seg fault.
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=53976
--
Edit this bug report at https://bugs.php.net/bug.php?id=53976&edit=1
