View Issue Details

IDProjectCategoryView StatusLast Update
0000848XdebugUncategorizedpublic2012-06-11 19:41
Reporterluzat Assigned To 
PrioritynormalSeveritycrashReproducibilityalways
Status resolvedResolutionno change required 
PlatformPHP 5.4.4-RC1OSDebian GNU/LinuxOS Versionunstable
Product Version2.2.0 
Summary0000848: 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
2) Build xdebug:

phpize
./configure
make

3) Run tests: make test
4) See several tests fail (including those for bug 0000838-0000840). PHP still crashes when displaying variables in Eclipse, too (setting a breakpoint works fine).

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.

TagsNo tags attached.
Operating SystemDebian GNU/Linux unstable
PHP Version5.4-dev

Activities

derick

2012-06-01 20:57

administrator   ~0002222

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)?

luzat

2012-06-03 14:08

reporter   ~0002231

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.

derick

2012-06-11 16:02

administrator   ~0002243

So I suppose I should close this one?

luzat

2012-06-11 17:23

reporter   ~0002247

Yes, this issue is a non-issue as reported.