View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001117 | Xdebug | Uncategorized | public | 2015-02-26 16:03 | 2015-02-28 16:30 |
| Reporter | z0rc | Assigned To | |||
| Priority | high | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Platform | Linux | OS | Debian | OS Version | 7.6 |
| Product Version | 2.3.1 | ||||
| Fixed in Version | 2.3.2 | ||||
| Summary | 0001117: phpunit with coverage reporting under 5.5.22 crashes xdebug | ||||
| Description | After upgrading from PHP 5.5.21 to 5.5.22 PHPUnit started to crash within xdebug module when used with coverage option. I tried with coverage-html and coverage-clover. Tried with PHPUnit branches 3.7 and 4.5. Sample output php vendor/bin/phpunit --configuration=phpunit.xml.distPHPUnit 4.5.0-16-geb6ad0d by Sebastian Bergmann and contributors. Configuration read from /var/build/total_import/staging/135/phpunit.xml.dist Deprecated configuration setting "strict" used ....... glibc detected php: realloc(): invalid next size: 0x00000000028518a0 *** Full GDB stack trace https://privatepaste.com/280caa3907 Interesting is that under valgrind there is no crash, but there is some nasty errors (valgrind -v --leak-check=full php vendor/bin/phpunit --configuration=phpunit.xml.dist) https://privatepaste.com/bf998591bd | ||||
| Steps To Reproduce | phpunit --coverage-html | ||||
| Tags | No tags attached. | ||||
| Operating System | |||||
| PHP Version | 5.5.20-5.5.25 | ||||
|
|
Here are similar reports https://github.com/puphpet/puphpet/issues/1368 |
|
|
Is this with all code coverage, or just some specific ones? Could you for example make a small reproducible case (ie, one specific unit test), that shows this crash? |
|
|
I've hit this issue with two internal projects. Will try to come up with some small testcase. |
|
|
Hi, I created reproducible case: |
|
|
Thanks bushman, how do I run that? Just in a dir with phpunit? |
|
|
You can install this case project by running: And then run: |
|
|
Thanks for the reproduce case. This is now fixed on GIT - for the 2.3.2 release. |