Description of problem: I'm not sure how to reproduce it reliably, but i have a project based on Symfony framework with Doctrine ORM. I happens when i try to make a request to the built in server or i try to update db schema. When i disable xdebug extension, everything runs fine. Version-Release number of selected component: php-cli-7.3.6-1.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: php bin/console doctrine:schema:update --force crash_function: zval_get_type executable: /usr/bin/php journald_cursor: s=043f1f35eaa34791a16bc4a89c408fc6;i=2c39f;b=3556f0eb70f14900834e05ff53081eba;m=2767054d8;t=58afd1676679f;x=67526dc0d24ac6b3 kernel: 5.1.7-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 zval_get_type at /usr/include/php/Zend/zend_types.h:411 #1 xdebug_var_export at /usr/src/debug/php-pecl-xdebug-2.7.2-1.fc30.x86_64/NTS/xdebug_var.c:1041 #3 xdebug_get_zval_value at /usr/src/debug/php-pecl-xdebug-2.7.2-1.fc30.x86_64/NTS/xdebug_var.c:1126 #4 add_single_value at /usr/src/debug/php-pecl-xdebug-2.7.2-1.fc30.x86_64/NTS/xdebug_stack.c:371 #5 xdebug_append_printable_stack at /usr/src/debug/php-pecl-xdebug-2.7.2-1.fc30.x86_64/NTS/xdebug_stack.c:451 #6 xdebug_throw_exception_hook at /usr/src/debug/php-pecl-xdebug-2.7.2-1.fc30.x86_64/NTS/xdebug.c:1638 #7 ??
Created attachment 1579157 [details] File: backtrace
Created attachment 1579158 [details] File: cgroup
Created attachment 1579159 [details] File: core_backtrace
Created attachment 1579160 [details] File: cpuinfo
Created attachment 1579161 [details] File: dso_list
Created attachment 1579162 [details] File: environ
Created attachment 1579163 [details] File: exploitable
Created attachment 1579164 [details] File: limits
Created attachment 1579165 [details] File: maps
Created attachment 1579166 [details] File: mountinfo
Created attachment 1579167 [details] File: open_fds
Created attachment 1579168 [details] File: proc_pid_status
Can you please open a upstream bug report about this issue ? => https://bugs.xdebug.org/
sure, here is the link to the issue report there https://bugs.xdebug.org/view.php?id=1675
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.