This time, both browser and eclipse are stuck, and Eclipse freezes at “Launching [project]” 57% (in this case), with details saying “Launching: waiting for XDebug session”.
Looks like a different problem, but for a moment I thought that solution was the same as here.
I apologize to those who have already been there and failed to solve the problem.
As can be found elsewhere, the problem is in the port. XDebug on machine running Eclipse is actually a server listening (by default) on port 9000, fed with debug data thru apache xdebug module.
In my case, particularly frustrating was the fact that debugging in Eclipse was working, and after not using it for a while it just stopped.
In my case, the solution was cleanup of unnecessary software. It turned out that some of it had occupied the port 9000, so XDebug was again able complete the full cycle of exchanging data.
So, as there is no general answer to the question what is already on the port 9000, I can suggest another solution: find one of the free ports (start searching from 9001, 9002, etc.) on machine running eclipse. Make sure you don’t forget to change configuration in both eclipse and apache xdebug module.
Changing the port as suggested solved this problem for me.
It was much simpler in my case. I just writing this, because I searched a while… Maybe some other find this useful.
xdebug.remote_enable was set to 0 => Off.
It’s only an error for newbies I think.
But related to your port problem, you can use netstat -a to list the ports used for something
I had same “symptoms” but my problem was apparently in the PHP executable. i had the PHP 5 selected while i was using PHP 5.3. Just changing it solved the problem.
Joe’s suggestion solved my problem. Thanks!
Big ups for posting this info – Google is nothing without a source!
Talking about ports, always remember the (DSL) router when debugging remote hosts! I spend hours looking for a solution, and all I had to do was to activate port forwarding on my Linksys
thx 🙂
I tried everything you guys suggested and still no joy but finally found the reason for my set up hanging at 57%…
So for me I had to add these lines to my /etc/php5/con.d/xdebug.ini file:
I don’t know what in my system went curly to make this a requirement but hopefully it can help someone else some day!
@Andy: Thanks for the comment. Actually, what you had there was not curly. It’s more or less according to the documentation – you must turn on and configure the PHP extension (module) in order to use it, and depending on linux distro, you could find it (the module) in different places.
thanks for all of you , I solved my problems by reset php.ini files what [xdebug.dll] version is not right
If Netweaver/Eclipse fails to connect to XDebug, you may wish to check the Apache logs for occurrences of something like: Cannot load Xdebug – it was built with configuration API220090626,TS,VC6, whereas running engine is API220090626,TS,VC9
[Fri Jun 01 18:38:05 2012] [notice] Child 3404: Child process is running
To remedy this, pick the right version of the XDebug binary from the XDebug website (try a few combinations till you get it working)
actually xdebug is a php module 🙂
Thanks for reading carefully! It took me a while to realize that I wrote it’s an apache module. Speaking of PHP, the term ‘extension’ is more appropriate, though.
Thanks, changing the port work for me and save me from frustration 😀
Changing port solved the problem.
Thanks!
Thanks. Changing ports start working