我使用Netbeans的XDebug和Easy XDebug FireFox插件

The add-on is essential when you debug MVC projects, because the normal way XDebug runs in Netbeans is to register the dbug session via the url. With the add-on installed in FireFox, you would set your Netbeans project properties -> Run Configuratuion -> Advanced and select "Do Not Open Web Browser" You can now set your break points and start the debugging session with Ctrl-F5 as usual. Open FireFox and right-click the Add-on icon in the right bottom corner to start monitoring for breakpoints. When the code reaches the breakpoint it will stop and you can inspect your variable states and call-stack.

尝试Eclipse PDT来设置具有您提到的调试特性的Eclipse环境。与var_dump的老方法相比，进入代码的能力是一种更好的调试方法，并在各个点打印，以查看流在哪里出错。当所有这些都失败了，虽然，我只有SSH和vim，我仍然var_dump()/die()找到哪里的代码出错。

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.

我使用Netbeans和XDebug。 在它的网站上查看如何配置它的文档。 http://php.netbeans.org/

集成的调试器，可以在逐步执行代码时观察变量值的变化，这真的很酷。但是，它们确实需要在服务器上安装软件，并在客户机上进行一定数量的配置。两者都需要定期维护以保持良好的工作状态。

print_r易于编写，并保证在任何设置中都能工作。

在某种程度上，这取决于事情的走向。这是我尝试分离的第一件事，然后在必要时使用echo/print_r()。

注:你们知道你可以把true作为第二个参数传递给print_r()，它会返回输出而不是打印它吗?例如:

echo "<pre>".print_r($var, true)."</pre>";