Skip to content

Instantly share code, notes, and snippets.

@0xlitf
Last active March 25, 2016 10:12
Show Gist options
  • Save 0xlitf/d02bda0cebccb286bd9c to your computer and use it in GitHub Desktop.
Save 0xlitf/d02bda0cebccb286bd9c to your computer and use it in GitHub Desktop.
debug release
https://msdn.microsoft.com/en-us/library/fsk896zz.aspx?f=255&MSPPError=-2147217396
How to: Debug a Release Build
Visual Studio 2015 Other Versions
You can debug a release build of an application.
To debug a release build
Open the Property Pages dialog box for the project. For details, see Working with Project Properties.
Click the C/C++ node. Set Debug Information Format to C7 compatible (/Z7) or Program Database (/Zi).
Expand Linker and click the General node. Set Enable Incremental Linking to No (/INCREMENTAL:NO).
Select the Debugging node. Set Generate Debug Info to Yes (/DEBUG).
Select the Optimization node. Set References to /OPT:REF and Enable COMDAT Folding to /OPT:ICF.
You can now debug your release build application. To find a problem, step through the code (or use Just-In-Time debugging) until you find where the failure occurs, and then determine the incorrect parameters or code.
If an application works in a debug build, but fails in a release build, one of the compiler optimizations may be exposing a defect in the source code. To isolate the problem, disable selected optimizations for each source code file until you locate the file and the optimization that is causing the problem. (To expedite the process, you can divide the files into two groups, disable optimization on one group, and when you find a problem in a group, continue dividing until you isolate the problem file.)
You can use /RTC to try to expose such bugs in your debug builds.
For more information, see Optimizing Your Code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment