通常我发现创建一个自定义日志功能可以保存在文件中，存储调试信息，并最终在公共页脚上重新打印。

您还可以重写常见的Exception类，以便这种类型的调试是半自动化的。

For the really gritty problems that would be too time consuming to use print_r/echo to figure out I use my IDE's (PhpEd) debugging feature. Unlike other IDEs I've used, PhpEd requires pretty much no setup. the only reason I don't use it for any problems I encounter is that it's painfully slow. I'm not sure that slowness is specific to PhpEd or any php debugger. PhpEd is not free but I believe it uses one of the open-source debuggers (like XDebug previously mentioned) anyway. The benefit with PhpEd, again, is that it requires no setup which I have found really pretty tedious in the past.

print_r() +1。使用它来转储对象或变量的内容。为了使它更具可读性，使用pre标记，这样你就不需要查看源代码了。

echo '<pre>';
print_r($arrayOrObject);

还有var_dump($thing) -这对于查看子事物的类型非常有用

手动调试对我来说通常更快——var_dump()和debug_print_backtrace()是你需要用来武装你的逻辑的所有工具。

Xdebug和用于notepad++的DBGp插件用于繁重的bug查找，FirePHP用于轻量级的东西。又快又脏?没有什么比dBug更好的了。

您可以使用Firephp作为firebug的附加组件在与javascript相同的环境中调试php。

我还使用前面提到的Xdebug来分析php。