View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000848 | Xdebug | Uncategorized | public | 2012-05-31 20:28 | 2012-06-11 19:41 |
| Reporter | luzat | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Platform | PHP 5.4.4-RC1 | OS | Debian GNU/Linux | OS Version | unstable |
| Product Version | 2.2.0 | ||||
| Summary | 0000848: Tests for bug 0000838-0000840 fail (also, similar symptoms still seem to occur). | ||||
| Description | I am experiencing PHP crashes when debugging a Symfony2 app with Eclipse and asking it to display variables. I suspected this was related to bug 0000838-0000840 and installed HEAD (1e7c7a7b4876fc8ef3ac90562fca9930d267e2aa). This does not help and the tests for bug 0000838-0000840 still fail as before with Debian's build of 2.2.0. | ||||
| Steps To Reproduce | 1) Install Debian GNU/Linux unstable (amd64 here) with PHP 5.4.4-RC1 phpize 3) Run tests: make test | ||||
| Additional Information | I have double-checked to see that xdebug_var.c contains the fix and even re-cloned the repository to build from scratch. I have attached the logs that I considered relevant. "make test" does not seem to complete, but hangs at TEST 167/217. | ||||
| Tags | No tags attached. | ||||
| Operating System | Debian GNU/Linux unstable | ||||
| PHP Version | 5.4-dev | ||||
|
|
make test doesn't really work for use with Xdebug... it never has. Before you do "make test" could you do a "make install" and then run ./test.sh (after modifying the path in test.sh)? |
|
|
My bad: After installing I noticed that I've had the path to another xdebug install in my php.ini all the time. I don't get xdebug crashes at the same point anymore and at least the tests for 0000838 and 0000840 do not fail anymore; 0000839 still does. Given that I still get crashes at different points while debugging I'll look into that issue more closely once I find time. This should probably go into another bug report, though. |
|
|
So I suppose I should close this one? |
|
|
Yes, this issue is a non-issue as reported. |