View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001460 | Xdebug | Uncategorized | public | 2017-08-08 11:36 | 2017-10-17 12:03 |
Reporter | rinu | Assigned To | derick | ||
Priority | normal | Severity | crash | Reproducibility | always |
Status | resolved | Resolution | no change required | ||
OS | Ubuntu | OS Version | 16.04 | ||
Summary | 0001460: ext/opcache/Optimizer/dce.c:584: dce_live_ranges: Assertion `op_array->opcodes[def].result_type & ((1<<1)|(1<<2))' failed. | ||||
Description | Xdebug (master branch) compiles and installs ok with PHP 7.2 but running any non-trivial code under FPM will result in this error, making PHP unusable. | ||||
Tags | No tags attached. | ||||
Operating System | |||||
PHP Version | 7.2-dev | ||||
|
I'm going to need a back trace, and the smallest bit of code you can produce that triggers this (on the CLI) please. Information on how to make a backtrace is at https://bugs.php.net/bugs-generating-backtrace.php Please run "export USE_ZEND_ALLOC=0" on the shell first, before "php script-that-crashes.php". |
|
Cannot reproduce in CLI mode, only FPM. The "Generic way to get a core on Linux" has never worked for me. No idea why. So starting FPM manually with gdb was my only chance for backtrace. When FPM runs as a service, this code will reproduce the original crash:
} |
|
Getting a back trace can indeed be fiddly - as you say you have one, did you forget to attach it to the report? |
|
I didn't get a bt for this crash but I reported a php bug for the next issue I found here: https://bugs.php.net/bug.php?id=75048 How am I going to get a bt for this issue? I ran FPM with gdb and only got the bt for the other issue, not this one. |
|
I finally got a core dump file. I hope I made the back trace correctly and this issue can be resolved. (gdb) bt |
|
Currently, I am getting errors without Xdebug enabled and just running "php run-tests.php". I'll keep monitoring this, but I don't think it's an xdebug issue. |
|
Well, my script does not crash when I disable xdebug and will always crash with xdebug enabled. Can't see how this is not an xdebug issue. The other PHP bug mentioned in this issue got resolved. This issue remains, just tried again with 7.2.0RC4 and the latest xdebug master. |
|
The problem was indeed not in Xdebug, but with just PHP. You should be able to simulate it by passing the -e option on the PHP CLI. This adds extra opcodes in the op arrays for Xdebug (and other tools) to use. Xdebug forces this option to always be on. In any case, it just got fixed in PHP itself, so I'm closing this issue: https://github.com/php/php-src/commit/e53a9aaa4aa091a0799ed5a078dc66ed04ff32b8 |
Date Modified | Username | Field | Change |
---|---|---|---|
2017-08-08 11:36 | rinu | New Issue | |
2017-08-08 11:40 | derick | Note Added: 0004390 | |
2017-08-08 11:40 | derick | Assigned To | => derick |
2017-08-08 11:40 | derick | Status | new => feedback |
2017-08-08 12:46 | rinu | Note Added: 0004391 | |
2017-08-08 12:46 | rinu | Status | feedback => assigned |
2017-08-08 12:52 | derick | Note Added: 0004392 | |
2017-08-08 13:06 | rinu | Note Added: 0004393 | |
2017-09-22 08:41 | rinu | Note Added: 0004422 | |
2017-10-15 14:07 | derick | Note Added: 0004440 | |
2017-10-16 17:22 | rinu | Note Added: 0004441 | |
2017-10-17 12:03 | derick | Note Added: 0004442 | |
2017-10-17 12:03 | derick | Status | assigned => resolved |
2017-10-17 12:03 | derick | Resolution | open => no change required |
2020-03-12 16:35 | derick | Category | Usage problems (Wrong Results) => Variable Display |
2020-03-12 16:38 | derick | Category | Variable Display => Uncategorized |