Well, the title seems to say it all :-) Not quite: Windows XP SP3, PHP 5.2.0, Xdebug v2.0.3, Dev-PHP 2.3.0, MozillaControl712 installed and declared in Dev-PHP.
With "Mozilla Browser", when I activate the debugger (BTW, the debugger buttons really should stay disabled until the debugger is activated), I get 2 rows in the Debugger log, then one more line when I click on Step over, then nothing, the active line never moves and the status line displays "Waiting for localhost..." Clicking on the Context button does switch to the Evaluation tab, but the array stays desperately empty and CPU usage rises to 80/90% (but leaving Editor tab brings CPU back to normal).
With "Internet Explorer", when I activate the debugger, I get 2 rows in the Debugger log, then one more line when I click on Step over, the active line never moves but after a few seconds the status line displays "Terminé" (I am running a French XP, so I am not sure if "Terminé" is a translation issue or if this is XP playing cute).
The workaround is to begin with a "Step into", or "Run" with a breakpoint.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Would you mind answering more questions about getting xdebug to run with Dev-php. Becasuse right not it looks to me as though the debug buttons do not do anything at all.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Be warned: once your debugger is properly configured, sometimes (but not often) it does not start. I don't know why. I press the Bulb button, it goes off a few moments then it switches back on and nothing happens. When this happens, I usually switch to another development tool because I am in a hurry and I don't have the time then to debug Dev-PHP and anyhow I really wouldn't know where to look. This happens rarely, so it is not a big issue, but this means you should not just try the debugger and think that since it is not working it is not properly configured, the only way to know if the debugger is properly configured is to check with phpinfo().
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
Well, the title seems to say it all :-) Not quite: Windows XP SP3, PHP 5.2.0, Xdebug v2.0.3, Dev-PHP 2.3.0, MozillaControl712 installed and declared in Dev-PHP.
With "Mozilla Browser", when I activate the debugger (BTW, the debugger buttons really should stay disabled until the debugger is activated), I get 2 rows in the Debugger log, then one more line when I click on Step over, then nothing, the active line never moves and the status line displays "Waiting for localhost..." Clicking on the Context button does switch to the Evaluation tab, but the array stays desperately empty and CPU usage rises to 80/90% (but leaving Editor tab brings CPU back to normal).
With "Internet Explorer", when I activate the debugger, I get 2 rows in the Debugger log, then one more line when I click on Step over, the active line never moves but after a few seconds the status line displays "Terminé" (I am running a French XP, so I am not sure if "Terminé" is a translation issue or if this is XP playing cute).
The workaround is to begin with a "Step into", or "Run" with a breakpoint.
Stupid me! I should have filed this as a bug report. I will do it presently.
Would you mind answering more questions about getting xdebug to run with Dev-php. Becasuse right not it looks to me as though the debug buttons do not do anything at all.
Hi shaba1,
see http://sourceforge.net/forum/message.php?msg_id=3889975
and http://pierre.fauconnier.free.fr/wikini/wakka.php?wiki=DevphpEnXdebug
> Would you mind answering more questions...
You're welcome.
--
Thanks for your report,
Pierre.
Be warned: once your debugger is properly configured, sometimes (but not often) it does not start. I don't know why. I press the Bulb button, it goes off a few moments then it switches back on and nothing happens. When this happens, I usually switch to another development tool because I am in a hurry and I don't have the time then to debug Dev-PHP and anyhow I really wouldn't know where to look. This happens rarely, so it is not a big issue, but this means you should not just try the debugger and think that since it is not working it is not properly configured, the only way to know if the debugger is properly configured is to check with phpinfo().