View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001387 | Xdebug | Uncategorized | public | 2017-01-08 18:35 | 2021-04-14 16:09 |
| Reporter | kelunik | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | unable to reproduce | ||
| Platform | x64 | OS | Ubuntu | OS Version | 16.04 |
| Product Version | 2.5.0 | ||||
| Summary | 0001387: Segfault in GC | ||||
| Description | Running the Humbug PHPUnit test suite with xdebug loaded makes PHP segfault at the end of the tests. Note: Running on PHP 7.1.0, but only 7.1-dev is available in the select box. | ||||
| Steps To Reproduce |
| ||||
| Additional Information | GDB LOGphp: /home/kelunik/.php-build/release/Zend/zend_gc.c:276: gc_possible_root: Assertion `(ref)->gc.u.v.type == 7 || (ref)->gc.u.v.type == 8' failed. Program received signal SIGABRT, Aborted. | ||||
| Tags | SIGSEGV | ||||
| Operating System | Ubuntu 16.04 | ||||
| PHP Version | 7.1-dev | ||||
|
|
This doesn't happen on 7.0.5 with xdebug 2.5.0 |
|
|
I can not reproduce this. Can you please try the following: install valgrind (apt-get install valgrind). Then on the shell, run the following: export USE_ZEND_ALLOC=0 The first test: gdb --args php vendor/bin/phpunit and on the GDB prompt: "run". Then when it crashes, type "bt full". And attach the output as a file to this issue. The second test: valgrind php vendor/bin/phpunit and attach the output as a file to this issue. |
|
|
Done. :-) |
|
|
I can still not reproduce this, not even with Ubuntu 16.04 and the compiler it comes with. Can you try disabling Xdebug in php.ini and try to run the test again? Nothing in the valgrind or gdb output even hints that Xdebug is the culprit here as it is not mentioned at all in the traces. |
|
|
I've set up things on another server and can reproduce it there, too. Disabling xDebug fails some tests, but doesn't crash at the end. Maybe it's not xDebug directly, a GC issue that does only appear on certain memory allocations and xDebug changes those to show up? I'll upload my php.sh and xdebug.sh files which I used to set things up. ./php.sh 7.1.0 && ./xdebug.sh 2.5.0 Used the default php.ini-development from current master and added the extension at the top. |
|
|
I can reproduce that now on Joe's box, but no idea how and why this happens... |
|
|
My previous statement was wrong. This happens with 7.0.0-7.0.14, too. |
|
|
Is this issue still relevant to you? |
|
|
Closing this, as it is missing requested feedback. |