View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000965 | Xdebug | Uncategorized | public | 2013-07-18 12:40 | 2016-11-29 23:52 |
| Reporter | zeran | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Platform | php | OS | linux | OS Version | centos/ubuntu |
| Product Version | 2.2.3 | ||||
| Summary | 0000965: xdebug crash on trace | ||||
| Description | xdebug crash on tracing code like | ||||
| Tags | crash, null, return, trace | ||||
| Operating System | linux | ||||
| PHP Version | 5.3.10 | ||||
|
|
When you say "tracing", what exactly do you mean? Can you elaborate a bit more please? |
|
|
I mean something like this: and |
|
|
Hi I was having some problems with phpmyadmin, and after different attempts, I found that if I changed xdebug.collect_return="1" to xdebug.collect_return="0", everything went back to normal. The problem was that many links didn't work and the session restarted sometimes, but I couldn't find any log that helped from mysql or phpmyadmin. I'm posting the link to the thread since I explained the problem quite detailed there. In any case, I'll post my system specs here:
I'm also uploading my xdebug.ini for reference. stackoverflow question |
|
|
I can confirm this bug. After upgrading to Ubuntu 14.04, I had to turn off the xdebug.collect_return or my Apache would always segfault. Specs:
|
|
|
Is this still an issue with Xdebug 2.2.5 and the other latest versions? |
|
|
I can´t test that right now since I´m traveling, but in 3 weeks I can do it and report back. |
|
|
I could confirm the bug on 2.2.5 (segfault), but on 2.2.6 it has been fixed and "collect_return" acts normally as it should. |
|
|
I'm expecting this one to be fixed. Please reopen this issue if you can reproduce this with the latest versions of Xdebug and PHP. |