"I was able to test with Xdebug 2.3.3 and 2.3.3 (from Remi Repo)."

That should be "2.3.3 and 2.3.2".

Just tried 2.3.2 from PECL, which also segfaults:

PHPUnit 4.8.6 by Sebastian Bergmann and contributors.

Segmentation fault (core dumped)

Though, I notice that 2.3.3 supposedly fixed a crash on coverage reports. Is 2.3.3 not stable in PECL yet?

Can you provide step-by-step instructions as to how to reproduce this — including installing anything I might not have? Expect me to have an empty system with only PHP and Xdebug setup - and know nothing about ZF.

Derick, I took some time to put a test case together that mimics the actual case that we were seeing the best I could.

While setting up this test case, I found that it may not just be Xdebug + ZF1 Controller tests, but actually something to do with stopping and starting coverage (this is something that we do in some of our suites to speed up execution times during fixture loading and such). The sample test case I setup includes these stops and starts, and if you were to remove them, the tests pass fine. I am unsure why the stops/starts don't cause issues in our tests that don't hit the ZF1 Controller testing code, perhaps they're called differently in those tests.

Here's the repo: https://github.com/jaydiablo/xdebug-test-case

I mention in the readme how to reproduce the segfault, let me know if you require anything else to take a look at this.

Oh, also, I should mention that when I was testing where the segfault happened I would occasionally get this output:

glibc detected php: double free or corruption (out): 0x00000000167244b0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x38fb475e66]
/lib64/libc.so.6[0x38fb4789ba]
/usr/lib64/php/modules/xdebug.so(xdebug_code_coverage_end_of_function+0xc9)[0x7f52e6746e79]
/usr/lib64/php/modules/xdebug.so(xdebug_execute_ex+0x791)[0x7f52e6742be1]
php[0x663b6d]
php(execute_ex+0x38)[0x654f58]
php(dtrace_execute_ex+0x8e)[0x5d0d0e]
/usr/lib64/php/modules/xdebug.so(xdebug_execute_ex+0x5f3)[0x7f52e6742a43]

TRUNCATED

I'll add a full copy of this trace to the repo in case it sheds some light on anything.

Thanks!

Cheers, I can reproduce the issue with your test case.

Hello,

I'm a colleague of the OP, and we were revisiting this as we move towards upgrading our systems to PHP7. I was able to simplify the test suite provided, which you can see here:

https://github.com/aripringle/xdebug-test-case/tree/simplification

The failure scenario seems very specific to our original implementation - calling a static method, which in turn calls another static method, which resumes code coverage and then sets a static property. I added some slight variations that don't fail:

• A passing test in TheTest.php, which calls the exact same static methods as the failing test, the only difference being that it bypasses the intermediary static method.
• A separate TestCase (NoStaticPropertyOnResumeTest.php) that passes, the only difference being that it the "resumeCodeCoverage" method does not change the value of the static property after resuming code coverage.

Also of note is that the segfault only happens when resuming coverage with the XDEBUG_CC_UNUSED flag.

I still can reproduce it, but finding the problem is a whole lot harder as there is so much code involved.

Fixed for Xdebug 2.5.1.