1·Which would you rather write, debug, and maintain?
您愿意编写、调试和维护哪一个？
2·We will use this application as the debug target.
我们将使用这个应用程序作为调试目标。
3·In such situations, you need to debug your program to find the exact cause.
在这种情况下，您需要调试您的程序来找到准确的原因。
4·You can do things like start or stop the server, or start it in normal or debug mode.
您可以执行一些操作，如启动或停止服务器，或以正常或调试模式进行启动。
5·This will disconnect your debug session.
这将会断开您的调试会话。
1·Automatic debug and stop Function.
具有自动侦错与停机功能。
2·The following topics provide basic information about how to debug.
下列主题提供有关如何侦错的基本资讯。
3·After attaching to the process, you can set breakpoints and use these to debug your code.
附加至处理序之后，您就可以设定中断点，并使用这些中断点来侦错程序码。
4·However, other types of errors require that you debug your code - that is, that you examine the code while it is running to validate that the execution path and data is as it should be.
不过，其他类型的错误则会要求您侦错程序码，即在程序码执行期间对其进行检查，以验证执行路径和资料是正确的。
5·The Release configuration of your program contains no symbolic debug information and is fully optimized.
程式的发行组态不包含符号侦错资讯，而且会完全最佳化。
1·You can see the detailed error information at run time and debug it by reviewing the system log and event log.
您可以看到运行时的详细错误信息，并通过查看系统日志和事件日志进行调试。
2·While these files are available for the developer to modify and debug if necessary, in general they are fully functional and should not be touched.
虽然在必要的情况下，开发人员可以使用这些文件来修改并进行调试，但是一般这些文件是功能完全的，并且不应该触及的。
3·But if you write rules using an RDR framework, you know exactly where a rule is to be added, and it becomes easier to debug which rule is breaking the logic.
但是如果您使用rdr框架编写规则，就会准确知道在何处添加规则，从而可以更轻松地对破坏逻辑的规则进行调试。
4·If the activities are logged, it is easy to debug and restore the environment quickly.
如果记录了各个活动，就很容易进行调试和快速恢复环境。
5·The relative terseness of the XSL transform makes the underlying concepts more apparent and thus easier to debug and maintain.
xsl转换的相对简洁使得基础概念更为明显，从而更便于进行调试和维护。