This is true 90% of the time. From there, some libraries like ezpublish will cause all sort of problems with xdebug depending on where you put the breakpoint (

This is true 90% of the time. From there, some libraries like ezpublish will cause all sort of problems with xdebug depending on where you put the breakpoint (it might be due to the number of recursive call or stack depth), and you'd really want to enable or disable debugging case by case, from your IDE ideally. Then debugging on a non dev server means installing a new package, configuring it and disable it afterwards just in case it has ill adverse effects. Then some eclipse pdt versions were stuck when using xdebug on some configs. Overall it works, but in practice, there's not enough cases IMO where step by step debugging is valuable enough to bother dealing with the not so exceptional weird things.