What Are the Differences Between Debug and Release of a Solution in vs2005 Development?

Debug is often referred to as a debug version, which contains debugging information and is not optimized in any way to make it easier for programmers to debug programs. A release is called a release, and it is often optimized to make the program optimal in terms of size and speed, so that users can use it well. debug version:

MDD MLD or MTD Use the Debug Runtime Library od to turn off the optimization switch D"_debug"Equivalent to define debug, turn on the compile debugging switch (mainly for assert functions) zi create an edit and continue database, so that if the source is modified during the debugging process, you don't need to recompile gz to help catch memory errors gm turn on the minimize relink switch to reduce link time release version: md ml or mt Use the runtime library of the release version o1 or o2 optimization switch, Make the program the smallest or fastest d"ndebug"Turn off the conditional compilation and debugging switch (i.e. do not compile assert functions) gf merges duplicate strings and puts string constants into read-only memory to prevent them from being modified. Actually, debug and release have no essential boundaries, they are just a set of compilation options, and the compiler just acts according to the predetermined options.

In fact, we can even modify these options to get an optimized debug version or a release version with trace statements. Oh.

The dll generated by the debug mode has a compilation symbol, which is of great help for debugging, and the dll that comes out of the release mode is the most efficient, because it has been optimized You can find the compilation mode selection on the left side of the run button.

When compiling and executing a project, it can be executed in both debug and release configurations.

The debug mode is used to debug the program, which is a protected runtime environment that will tell you if the program is leaking or not, and can also check the results of specific functions at runtime. However, the executable it generates is slower.

So when your app is tested and ready to be put into use, you should compile it in release mode, which will produce an executable file for end users to use.

To put it simply, you can debug, check bugs, and correct errors under debug, and it runs slowly.

Although it is also possible to break points under release, sometimes the value of some variables is not visible under release. Debug should be used for debugging.

Refer to the OpenCV Computer Vision Programming Manual

There are two versions of the program in VS: debug and release.

1. Different versions.

Debugging is often referred to as a debug version, and through a series of compilation options, the compiled result usually contains debugging information and does not do any optimization, so as to provide developers with powerful application debugging capabilities.

Release, usually called release version, is for user use, and general customers are not allowed to debug on the release version.

2. The operation effect is different.

3. The algorithm is different.

Debug is different from what release does when initializing variables, debug assigns each byte bit to 0xcc, and release is assigned to a value that is approximately random.

The release version is called the release version, and the debug version is called the debug version.

Debug can be single-stepped, tracking and other functions, but the generated executable file is relatively large, and the running speed is slow. The release version runs faster and the executable is smaller, but under its compilation conditions.

Unable to perform debugging functions.

The release exe file links to the standard mfcdll (usemfcinasharedorstaticdll). These DLLs are installed when Windows.

wait, it has been configured, so that these programs can run on machines that do not have VisualC++ installed.