Differences between debug and release versions in Visual Studio

Debug is usually called a debug version. It contains debugging information without any optimization, so that programmers can debug programs easily. Release is called a release version. It is often optimized to optimize the code size and running speed, so that users can use it well.
The real secret of debug and release lies in a set of compilation options. The options for the two are listed below (of course, there are other options, such as/FD/Fo, but the difference is not important. Usually they will not cause the release version error and will not be discussed here)
Debug version

Parameter description
/MDD/MLD or/MTD use the debug Runtime Library (the runtime function library of the debug version)
/OD turn off the optimization Switch
/D "_ debug" is equivalent to # DEFINE _ Debug. Enable the compile and debug code switch (mainly for the assert function)
/Zi creates the edit and continue database, so that the source code does not need to be re-compiled if the source code is modified during the debugging process.
/GZ helps capture Memory Errors
/GM enables the minimize reconnection switch to reduce the link time
 
Release Version

Parameter description
/MD/ml or/MT use the runtime function library of the released version
/O1 or/O2 optimization switch to minimize or minimize the program
/D "ndebug" Disable the Conditional compilation and debugging code switch (that is, do not compile the assert function)
/GF combines repeated strings and puts string constants in read-only memory to prevent Modification
 
In fact, there is no essential limit between debug and release. They are just a set of compilation options, and the compiler only acts according to the predefined options. In fact, we can even modify these options to get optimized debugging versions or release versions with trace statements.

Under which circumstances will the release version go wrong?
With the above introduction, let's compare these options one by one to see how release errors are generated.
1. Runtime Library: Specifies the runtime function library to be linked, which usually only affects the performance of the program. The Runtime Library of the debug version contains debugging information and uses some protection mechanisms to help identify errors. Therefore, the performance is inferior to that of the release version. The Runtime Library provided by the compiler is usually stable and does not cause release errors. However, the debug Runtime Library enhances error detection, such as heap memory allocation, sometimes there may be debug errors but release is normal. It should be pointed out that, if the debug is wrong, even if the release is normal, the program must have
Bug, but it may be that a certain release version of the release version is not shown.
2. Optimization: This is the main cause of errors, because the source program is basically translated directly when optimization is disabled, and the compiler will make a series of assumptions after optimization is enabled. There are several types of errors:
1. Frame pointer (FPO for short): All call information (return address, parameters) and automatic variables are stored in the stack during function calling. If the declaration and implementation of a function are different (parameters, return values, and call methods), an error occurs. However, in the debug mode, stack access is implemented through the address saved by the EBP register, if no errors such as array out-of-bounds (or "not many" out-of-bounds) occur, the function can normally be executed. In the release mode, optimization will omit the EBP stack base address pointer, in this way, accessing the stack through a global pointer will cause the program to crash if the returned address is incorrect.

The strong type feature of C ++ can check the majority of such errors, but if forced type conversion is used, it will not work. You can force the/Oy-compilation option in the release version to disable frame pointer omitting to determine whether such errors are possible. This type of error is usually caused by an error in writing the message response function of MFC. Correct:

Afx_msg lresult onmessageown
(Wparam, lparam );
 
On_message macro contains forced type conversion. One of the methods to prevent this error is to redefine the on_message macro and add the following code to stdafx. H (after # include "afxwin. H"). An error will be reported when the function is compiled incorrectly.

# UNDEF on_message
# Define on_message (message, memberfxn )\
{
Message, 0, 0, 0, afxsig_lwl ,\
(Afx_pmsg) (afx_pmsgw)
(Static_cast <lresult (afx_msg_call \
Cwnd: *) (wparam, lparam)> (& memberfxn)
},

2. Volatile variable: Volatile tells the compiler that the variable may be modified by unknown methods (such as systems, other processes and threads) outside the program ). To improve program performance, the optimizer usually places some variables in registers (similar to the Register keyword), while other processes can only modify the memory where the variable is located, but the value in the Register remains unchanged.

If your program is multi-threaded, or you find that the value of a variable is inconsistent with the expected value and you are sure that the setting is correct, you may encounter such a problem. This type of error is sometimes manifested as the program has the fastest optimization error and the smallest optimization is normal. Add volatile to the variables you think are suspicious.
3. Variable Optimization: The optimization program will optimize the variable based on the usage of the variable. For example, a function has an unused variable. In the debug version, it may mask an array out of bounds. In the release version, this variable may be optimized, in this case, the array out-of-bounds will destroy the useful data in the stack. Of course, the actual situation is much more complicated than this. The related errors include illegal access, including array out-of-bounds and pointer errors. For example:

Void FN (void)
{
Int I;
I = 1;
Int A [4];
{
Int J;
J = 1;
}
A [-1] = 1;
// Of course the error is not so obvious, for example, the subscript is a variable
A [4] = 1;
}
 
 
J has an out-of-range scope when the array is out of bounds, but its space is not reclaimed, So I and j will cover up the out-of-bounds. The release version may be optimized because I and j are not very useful, so that the stack is damaged.

3. debug and ndebug: When _ debug is defined, the assert () function is compiled, but ndebug is not compiled. In addition, the compilation of the trace () macro is also controlled by _ debug.

All these assertions are compiled only in the debug version, but are ignored in the release version. The only exception is verify (). In fact, these macros call the assert () function, but attach some library-related debugging code. If you add any program code to these macros, instead of a Boolean expression (for example, a value assignment or a function call that can change the value of a variable), the release version will not perform these operations, this may cause errors. It is easy for beginners to make such mistakes, and the search method is also very simple, because these macros are listed above, you only need to use the find in files function of VC ++ to find the place where these macros are used in all files of the project and then check them one by one. In addition, some experts may also join
# Pay Attention to Conditional compilation such as ifdef _ debug.
By the way, it is worth mentioning that the verify () macro allows you to put program code in a Boolean expression. This macro is usually used to check the return values of Windows APIs. Some people may abuse verify () For this reason. In fact, this is dangerous because verify () violates the idea of assertions and cannot completely separate program code from debugging code, in the end, it may cause a lot of trouble. Therefore, experts suggest using this macro as little as possible.

4./GZ option: This option will do the following:
1. initialize memory and variables. Including using 0xcc to initialize all automatic variables, 0xcd (cleared data) to initialize memory allocated in the heap (that is, dynamically allocated memory, such as new), 0xdd (dead data) fill in the released heap memory (such as delete), 0xfd (defencde data), and initialize the protected memory (debug adds the protected memory before and after the dynamically allocated memory to prevent cross-border access ), the words in the brackets are the notes suggested by Microsoft. The advantage of doing so is that these values are very large and cannot be used as pointers (and in 32-bit systems, pointers are rarely odd values, in some systems, odd-number pointers produce runtime errors), which are rarely used as numerical values, and these values are easy to recognize. Therefore, it is helpful
Errors encountered only when the release version is found in the debug version. Note that many people think that the compiler will use 0 to initialize the variable, which is wrong (and this is not conducive to finding errors ).
2. When a function is called through the function pointer, the matching of the function call is verified by checking the stack pointer. (Prevent original form mismatch)
3. Check the stack pointer before the function returns, and confirm that it has not been modified. (Avoid out-of-bounds access and original form mismatch. When combined with the second item, you can roughly simulate frame pointer omitting FPO.) The common/GZ option will cause errors in the debug version and the release version is normal, because uninitialized variables in the release version are random, this may cause the pointer to point to a valid address and mask illegal access. In addition, options such as/GM/GF have fewer errors, and their effects are obvious and easy to find.

How to "debug" release programs
When debugging succeeds but the release fails, it is obviously very frustrating and often cannot be started. If you have read the above analysis and combined the specific performance of the error, it is good to quickly find the error. However, if you cannot find it at the moment, the following provides some strategies in this case.

1. As mentioned above, debug and release are only the differences between a set of compilation options. In fact, there is no definition to distinguish them. We can modify the compilation option of release to narrow down the error range. As mentioned above, you can change the release options to the corresponding debug options one by one, for example,/MD to/MDD,/O1 to/OD, or run time optimization to program size optimization. Note: You can change only one option at a time to see which option the error disappears, and then find the option-related error accordingly. These options can be selected directly from the list in project \ Settings.... Do not manually modify them. Since the above analysis is quite comprehensive, this method is the most effective.

2. In the programming process, you should always pay attention to testing the release version, so as to avoid too much code and time constraints.
3. Use the/W4 warning level in the debug version to obtain the maximum error information from the compiler. For example, if (I = 0) will cause/W4 warning. Do not ignore these warnings. This is usually caused by bugs in your program. But sometimes/W4 will bring a lot of redundant information, such as unused function parameter warnings, and many message processing functions will ignore some parameters. We can use:

# Progma warning (Disable: 4702)
// Disable
//...
# Progma warning (default: 4702)
// Re-Allow to temporarily disable a warning or use
# Progma warning (push, 3)
// Set the warning level to/W3
//...
# Progma warning (POP)
// Reset to/W4
 
 
To temporarily change the warning level. Sometimes you can only use/W4 in the code that is considered suspicious.
4. You can debug your release version just like debug. In Project/settings..., select Settings for "Win32 release", C/C ++, General for category, and program database for debug info. Add "/OPT: ref" at the end of the link tag project options (do not enter the quotation marks ). In this way, the debugger can use the debugging symbol in the PDB file.

However, during debugging, you will find it difficult to set breakpoints and to find variables ?? These are all optimized. Fortunately, the call Stack window still works normally. Even if the frame pointer is optimized, the stack information (especially the return address) can still be found. This is helpful for locating errors.
========================================================== ========================================
For original documents of others, refer:


Differences between debug and release versions and debugging problems:
. Memory Allocation Problems

1. The variable is not initialized. The following program runs well in debug.

Thing * search (thing * something)
Bool found;
For (INT I = 0; I <whatever. getsize (); I ++)
{
If (whatever [I]-> Field = something-> field)
{/* Found it */
Found = true;
Break;
}/* Found it */
}
If (found)
Return whatever [I];
Else
Return NULL;
But not in release, because in debug, found = false is automatically initialized for the variable, but not in release. Initialize variables, classes, or structures as much as possible.

2. Data Overflow

For example, char buffer [10];
Int counter;

Lstrcpy (buffer, "abcdefghik ");

In the debug version, the buffer's null overwrites the counter's high position, but unless counter> 16 m, there is no problem. However, in the release version, counter may be placed in the register, so that null overwrites the space in the buffer, which may be the return address of the function, leading to access error.


3. The memory allocation methods for debug and release versions are different. If you apply for 6 * sizeof (DWORD) = 24 bytes for ele in debug, you are actually allocated 32 bytes (32bytes for Debug ), in the release version, 24 bytes are allocated to you (8 bytes for the release version). Therefore, if you write ele [6] In the debug version, there may be no problems, in the release version, access violate exists.


Ii. Assert and verify

1. Assert will not be compiled in the release version.

The assert macro is defined in this way.

# Ifdef _ debug
# Define assert (x) if (x) = 0) report_assert_failure ()

# Else
# Define assert (X)
# Endif
Actually complicated, but irrelevant. If you add the Code required by the program to these statements
For example

Assert (pnewobj = new cmyclass );

Pnewobj-> myfunction ();

In this case, pnewobj in the release version is not allocated to space.

Therefore, when the next statement is executed, the program reports that the program has performed illegal operations. In this case, you can use verify:

# Ifdef _ debug
# Define verify (x) if (x) = 0) report_assert_failure ()

# Else
# Define verify (x) (X)
# Endif
In this way, the code can be executed in the release version.

Iii. Parameter issues:

The custom message processing function must be defined as follows:

Afx_msg lresult onmymessage (wparam, lparam );

The returned value must be hresult type. Otherwise, the debug will pass, and the release will fail.

Iv. Memory Allocation

Ensure uniformity of Data creation and clearing: If a DLL provides a function that can create data, the DLL should also provide a function to destroy the data. Data creation and cleanup should be at the same level.


V. dll disaster

People will mix different versions of DLL to create a non-consistent image called "dynamic Connection Library hell" (DLL hell), even Microsoft said so (http://msdn.microsoft.com/library/techart/dlldanger1.htm ).


If your program uses your own DLL, note the following:

1. You cannot mix debug and release DLL versions. Both debug and release versions are release.


The solution is to put the debug and release programs under the debug and release directories of the main program respectively.


2. Never think that static connection to the database will solve the problem, which will only make the situation worse.

Debugging in the vi. Release Board:

1. Change assert () to verify (). Find the code defined in "# ifdef _ debug". If you need the code in the release version, move it out of the definition. Find the code in trace (...) because the code is not compiled in release. Check whether the Code required in the release is not cheap.


2. The differences brought about by variable initialization exist in different systems or between debug/release versions. Therefore, initialize the variables.


3. Is there a warning during compilation? Set the warning level to 3 or 4, and ensure that no warning appears during compilation.

VII. Change the optimization option under the "C ++/C" project in project settings to disbale (Debug ). Compiler Optimization may cause many unexpected errors, please refer to http://www.pgh.net /~ Newcomer/debug_release.htm


1. You can also debug the software of the release version. Make the following changes:

Set "category" to "general" under "Project Settings" C ++/C "and" debug info "to" program database ".


Select the "Generate debug info" check box under the "Link" project.

"Rebuild all"

Some restrictions arising from this practice:

The value of the variable in the mfc dll cannot be obtained.

All DLL projects used by the software must be modified.

In addition:

Ms bug: A Ms technical document shows that the "maximize speed" optimization option for DLL in vc5 is not fully supported, therefore, this will cause memory errors and cause program crashes.


2. www.sysinternals.com has a program called debugview, which is used to capture output of outputdebugstring. After running (it is estimated that it is set to system debugger), you can view output of outputdebugstring of all programs. After that, you can run your program and view debugging information without using VC.


3. There is a static code check tool named gimpel lint, which is said to be easy to use. Http://www.gimpel.com is just $.


References:

1)
Http://www.cygnus-software.com/papers/release_debugging.html

2) http://www.pgh.net /~ Newcomer/debug_release.htm