I am using a Intel Mac running leopard and using Komodo 4.4.1. I previously set up xdebug for remote debugging on my local machine and it was working. I don't recall I mess with the setting anymore afterwards but now it just stops working.
I made sure Komodo is listening to the right port, and the "Listen for Debugging Connections" is checked under the debug menu. when I do php -m, it shows that xdebug is listed both as PHP modules and Zend modules. I have seen some posts on the forum saying that it's bad, but so far i have no luck just load xdebug as Zend module. I have tried moving the xdebug.so to somewhere else other than the php default extension location, but still doesn't work. I don't even know if this is the problem but i definitely had xdebug working before.
my php.ini set up looks like this
zend_extension=/usr/local/php5/lib/php/extensions/xdebug/xdebug.so
xdebug.remote_enable=1
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.remote_host=127.0.0.1
xdebug.remote_port=9000
xdebug.idekey=komodo
xdebug.remote_log=/usr/local/php5/xdebug.log
notice that xdebug.log never got created. and from the apache error log, it complains that "File does not exist: .....blah.... http://localhost/?XDEBUG_START_SESSION=komodo"
it sounds to me that something is not wired up correctly..
anybody can shed some light on this?
-mo
Your setup looks fine, the listing of xdebug in both the PHP Modules and the Zend Modules is fine (my PHP/Xdebug setup shows the same output).
I think the problem is your triggering of debugging (i.e. the query), it should be using XDEBUG_SESSION_START, not XDEBUG_START_SESSION:
Does that fix it?
omg, I feel like the dumbest person in the world. but yea, that's the problem.
I've had that happen to me before. I now make use of the Firefox Xdebug extension to turn Xdebugging on/off without the need to remember this stuff:
https://addons.mozilla.org/en-US/firefox/addon/3960
Cheers,
Todd