View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001505 | Xdebug | Uncategorized | public | 2017-12-29 23:06 | 2018-01-23 16:47 |
| Reporter | rtsikma | Assigned To | |||
| Priority | immediate | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | unable to reproduce | ||
| Platform | x64 | OS | Windows | OS Version | 10 |
| Product Version | 2.6.0beta1 | ||||
| Summary | 0001505: CLI has stopped working error when xdebug extension is loaded | ||||
| Description | When attempting to start PHP with the xdebug extension and my own created extension, a "CLI has stopped working error" is displayed. | ||||
| Steps To Reproduce | Run php -i with a custom extension | ||||
| Additional Information | A crash dump is available for this issue here: This is on a 64 bit Windows 10 PC, running a 32-bit PHP. This PHP install has a custom extension extension | ||||
| Tags | No tags attached. | ||||
| Operating System | Windows 10 | ||||
| PHP Version | 7.2.0-7.2.4 | ||||
|
|
Hi, If you want me to have a look at this, I need to be able to reproduce this on a Linux platform. That means, I need to have your extension's source code. cheers, |
|
|
Considering that the entension is proprietary code from the company I work for, that may prove difficult. What I get from the debug call stack is this: [Inline Frame] php7.dll!zend_mm_alloc_small(_zend_mm_heap ) Line 1273 |
|
|
Sorry, I can't help then. Feel free to reach out privately in case you can provide this privately — email is at https://xdebug.org/support.php#email |
|
|
In case you were curious about this, I was able to resolve this issue. The problem was a zend_string pointer not being properly freed (efree() was called on the zend_string->val instead of calling zend_string_release(). When I updated to PHP 7.2.1 the crash location changed from inside the xdebug extension to the mysqldn extension. Fun times :) |
|
|
OK. Good to know it wasn't in Xdebug then. Cheers! |