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

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

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

在生产环境中，我使用error_log()将相关数据记录到服务器的错误日志中。

由Derick Rethans编写的Xdebug非常好。我前段时间用过，发现安装起来不那么容易。一旦你完成了，你就不会明白没有它你是如何做到的:-)

在Zend开发者专区有一篇很好的文章(在Linux上安装似乎并不容易)，甚至还有一个Firefox插件，我从来没用过。

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.

Komodo IDE works well with xdebug, even for the remore debugging. It needs minimum amount of configuration. All you need is a version of php that Komodo can use locally to step through the code on a breakpoint. If you have the script imported into komodo project, then you can set breakpoints with a mouse-click just how you would set it inside eclipse for debugging a java program. Remote debugging is obviously more tricky to get it to work correctly ( you might have to map the remote url with a php script in your workspace ) than a local debugging setup which is pretty easy to configure if you are on a MAC or a linux desktop.

坦率地说，是print和print_r()的组合，以打印出变量。我知道很多人更喜欢使用其他更高级的方法，但我发现这是最容易使用的。

我要说的是，直到我在Uni做了一些微处理器编程，甚至都不会使用它，我才完全理解这一点。