View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001382 | Xdebug | Code Coverage | public | 2017-01-03 03:34 | 2017-02-08 22:03 |
| Reporter | joshuaspence | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Product Version | 2.5.0 | ||||
| Summary | 0001382: Segmentation fault when calculating code coverage | ||||
| Description | We recently updated XDebug from 2.4.0 to 2.5.0 and are consistently experiencing segmentation faults on the later version. | ||||
| Steps To Reproduce | I don't have exact steps to reproduce at the moment, as it is basically just "run our entire test suite with code coverage enabled". I can, however, provide further information if required. I have attached the full stack trace. | ||||
| Tags | No tags attached. | ||||
| Operating System | |||||
| PHP Version | 5.6.20-5.6.24 | ||||
|
|
I am afraid that I would need to be able to reproduce this locally in order to fix this :-/ I would also recommend you use an Xdebug without debug symbols stripped, as the "No symbol table info available" makes it impossible for me to even find which line things occur at. You can probable prevent symbols from being stripped by changing the "-O2" to "-O0 -ggdb3" in the Makefile after your "configure" run. |
|
|
Ping? |
|
|
I get this same error when running my test suites on against 2.5.0 but not against 2.4.1 I tested against the 2.6.0-dev from today though and no longer get any errors, so I think this can be marked as fixed. |
|
|
Okay, thanks. I'm closing this issue then. |
