When you have that option you may be tempted to use a debug build on staging and a release build in production.
如果你可以选择，你可能希望在交付准备服务器上使用调试构建版本，在生产环境上使用发布构建版本。
As I have described in this article, this is essentially the difference between an integration build and a release build.
正如我在本文中所描述的，这是集成构建和发布构建的本质上的区别。
By retaining a copy of the mapping.txt file for each release build, you ensure that you can debug a problem if a user encounters a bug and submits an obfuscated stack trace.
通过保存发布构建版本的mapping .txt文件拷贝，确保当用户碰到bug，并把混淆后的堆栈调试跟踪信息提交给你时，你可以进行调试从而修复问题。
Collier mentioned that "the goal of OpenStack is to support multiple hypervisors, although currently the release build is lacking support for both VMware and Microsoft's Hyper-V."
Collier提到，“OpenStack的目标是要支持多种虚拟服务器，尽管当前发布的版本还不支持VMware和微软的Hyper - V。”
A release build USES optimizations.
发布版本使用优化。
Optimizations are generally turned on in a release build.
发布版本中的优化通常是打开的。
You should use a release build to detect performance problems in your application.
应该使用发行版本来检测应用程序中的性能问题。
If you then build your application for a release build, you may get an access violation.
如果那时生成应用程序的发布版本，则可能会发生访问冲突。
This is the least likely cause of release build problems, but it does arise on occasion.
这导致发布版本问题的可能性最低，但有时确实会发生。
This section presents information on why and when you would want to change from a debug build to a release build.
本节介绍有关为什么以及何时需要将调试版本更改为发布版本的信息。
When you use optimizations to create a release build, the compiler will not produce symbolic debugging information.
当使用优化创建发布版本时，编译器不会产生符号调试信息。
If your code generates compile errors after switching from debug build to release build, there are some areas you should check.
如果从调试版本切换到发布版本后代码生成编译错误，有几个方面应该检查。
In a release build, stray Pointers have a greater chance of pointing to uninitialized memory instead of pointing to debug information.
在发布版本中，游离的指针有更多机会指向未初始化的内存，而不是指向调试信息。
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.
由于堆布局在发布版本和调试版本间不同，因此内存覆盖在调试版本中可能不会引起任何问题，但在发布版本中可能导致灾难性的后果。
“发布”生成配置。
Release build should contain debug symbols.
发布版中应该包含调试符号。
By default, a Release build employs various optimizations.
根据预设，发行版会进行各种最佳化。
This indicates that native symbols were stripped during the Release build of the application.
这表明，在应用程序发布期间，本地符号被去除。
When a project or solution is fully developed and sufficiently debugged, its components are compiled in a Release build.
在项目或解决方案完全开发并充分调试后，在“发布”版本中编译其组件。
At Release Build Minus One - ideally, the last version before the public beta hits the streets - there are only five "blocking" bugs, all of which Rakowski and team deem fixable.
发布版本——在公开的beta版本面世之前的最后一个版本只剩5个阻碍性错误(blocking bugs)，Rakowski的团队认为这些bug都是可以解决的。
This makes it difficult to debug an optimized (release) build of your program.
这使得调试程序的优化(发布)版本相当困难。
You may receive compiler warnings during an optimized (release) build that you did not receive during a debug build.
在最佳化(发行)版期间，您可能会收到在侦错版期间未曾收到的编译器警告。
You may receive compiler warnings during an optimized (release) build that you did not receive during a debug build.
在最佳化(发行)版期间，您可能会收到在侦错版期间未曾收到的编译器警告。
应用推荐