When you have that option you may be tempted to use a debug build on staging and a release build in production.
如果你可以选择，你可能希望在交付准备服务器上使用调试构建版本，在生产环境上使用发布构建版本。
When you run a debug build, those modules are considered to be user code.
运行调试版本时，将这些模块视为用户代码。
This section presents information on why and when you would want to change from a debug build to a release build.
本节介绍有关为什么以及何时需要将调试版本更改为发布版本的信息。
You may receive compiler warnings during an optimized (release) build that you did not receive during a debug build.
在最佳化(发行)版期间，您可能会收到在侦错版期间未曾收到的编译器警告。
If your code generates compile errors after switching from debug build to release build, there are some areas you should check.
如果从调试版本切换到发布版本后代码生成编译错误，有几个方面应该检查。
The following procedures describe how to enable native run-time checks in a debug build, and how to modify native run-time check behavior.
下面的过程介绍了如何在调试版本中启用本机运行时检查，以及如何修改本机运行时检查的行为。
There are other differences, but following are the primary differences that would cause an application to fail in a release build when it works in a debug build.
还有其他差异，但以下是导致应用程序在调试版本中可以运行但在发布版本中失败的主要差异。
Because heap layout is different between release and debug versions, a memory overwrite might not create any problems in a debug build, but may have catastrophic effects in a release build.
由于堆布局在发布版本和调试版本间不同，因此内存覆盖在调试版本中可能不会引起任何问题，但在发布版本中可能导致灾难性的后果。
Developers will compile a Debug build repeatedly, at each step in their development process.
开发人员会重复地在开发流程的每一步骤中编译侦错版。
For example, you might create one directory called perl-5.9.0/debug-build and another called perl-5.9.0/std-build>.
例如，您可能会创建一个名为 perl-5.9.0/debug-build 的目录，以及另一个名为 perl-5.9.0/std-build 的目录。
For example, you might create one directory called perl-5.9.0/debug-build and another called perl-5.9.0/std-build>.
例如，您可能会创建一个名为 perl-5.9.0/debug-build 的目录，以及另一个名为 perl-5.9.0/std-build 的目录。
应用推荐