I've been trying to debug a problem with my .install file for a module I wrote using Komodo 4.1 and xdebug (with the Xdebug Helper Firefox add-on), and I'm having a problem. I turn on the debugger and click on Submit on the Modules admin page. The debugging starts at line 12 in index.php, I have a breakpoint in my install file, but for some reason it never gets there. Instead, the Debugging Options dialog box comes up instead, and debugging stops. I've read everything I can find on debugging in Komodo , but I can't figure out why the Debugging Options dialog box keeps coming up. Can anyone explain why this happens and how I can get around it so I can get on with my debugging?

Thanks.

Comments

anisotropic’s picture

I just tested this using Komodo IDE 4.2 on an Intel Mac, and was able to set a breakpoint and debug the code in book.install when installing the book module on a fresh install of Drupal 5.2. What combination of everything are you using:

* version of Komodo IDE
* verion of PHP
* operating system

Does debugging work otherwise, for example in module code? Does debugging behave differently if you set the XDEBUG_SESSION_START GET variable in the url manually instead of using the Firefox extension?

You should also ensure you have the latest builds of xdebug, as there are a number of fixes in the latest binaries:

OS X PPC:
http://downloads.activestate.com/Komodo/RemoteDebugging/4.2/MacOSX/Komod...

OSX Intel:
http://downloads.activestate.com/Komodo/RemoteDebugging/4.2/MacOSX/Komod...

Win32:
http://downloads.activestate.com/Komodo/RemoteDebugging/4.2/Windows/Komo...

Linux x86:
http://downloads.activestate.com/Komodo/RemoteDebugging/4.2/Linux/Komodo...

cgchoffman’s picture

You should only use the distribution of Xdebug that ActiveState ships: http://code.activestate.com/komodo/remotedebugging/
Or else you can expect problems while remote debugging php programs...Just in case some one comes across this like I did but don't happen to be Komodo Tech Support...

- Carey