关于调试我们来说几句。
Visual debugging of existing code.
已存在代码的可视化调试。
Scenario 1: Memory debugging tools
第 1种情况：内存调试工具
It will make debugging much simpler.
这可以让调试更加简单。
Start the server in debugging status.
以调试状态启动服务器。
It is very, very useful for debugging.
这个特性对调试非常有用。
Traditional way of debugging with DBX.
用dbx进行调试的传统方式。
Create Build Descriptor for debugging.
创建用于调试的构建描述符。
This situation makes debugging difficult.
此情况使得调试工作变得非常困难。
This message is much better for debugging.
这条消息对于调试更为合适。
Ability to start debugging after an error.
错误后进行调试的能力。
There are many debugging formats available.
有多种调试格式可供使用。
The debugging story has gotten better, too.
调试方面的事情同样也变得更好了。
Source code for the example debugging session.
调试会话示例的源代码。
The present: workarounds for mobile debugging.
现状：移动调试的变通方案。
Integrated test client with debugging support.
包含了调试支持的集成测试客户端。
A debugging session with the new functionality.
具有新功能的调试会话。
You can also set your TraceLevel for debugging.
您可以为调试设置TraceLevel。
That, by the way, is also a good debugging tool.
顺便说一下，这是一种很好的调试方法。
It is not a tutorial on setting up and debugging.
而不是关于设置和调试的教程。
A standard environment also simplifies debugging.
标准的环境还可以简化调试工作。
You simply write your program and start debugging.
您可以简单地编写您的程序并启动调试。
This can be a great help in the debugging process.
这对调试过程很有帮助。
Extra debugging time will produce a better product.
额外的调试时间将导致更好的产品。
Most debugging of mapping documents is done at run time.
大多数映射文件的调试都是在运行期间。
This allows you to begin debugging as early as possible.
这让您能够尽早开始调试。
It also has excellent debugging that's a snap to set up.
它还有非常好的调试功能，而且极易设置。
You can even use Eclipse's Python support for debugging.
甚至可以使用Eclipse的Python支持进行调试。
This can make for difficult debugging or poor performance.
这将导致难以调试和较差的性能。
Now start the debugging session from the Run > Debug menu.
现在通过Run > Debug...菜单启动调试会话。
应用推荐