Program debugging - debug/release version

explain

• In years of embedded R & D work , It is found that most small and medium-sized companies are not divided Debug/Release Version habit , Even some entrepreneurial teams who are known as industry leaders and large companies .
• Common processing ：

1. There is only one version in the whole development stage , Almost no extra tools are used , Debugging, etc. by printing without using gdb Tools such as .
2. Use the version with debugging information when programming debugging , The official version is based on this strip Next .

Personal understanding

Whether it is necessary to distinguish Debug/Release edition

• Debug（ Debugging phase ）、Release （ Release phase ）, There are two phases in the life cycle of each program , In order to deal with , Each program should have two versions （Debug Version and Release edition ）,Debug Version to facilitate debugging and find problems , A lot of additional debugging tools need to be added , and Release edition , For performance and user experience , Some optimization of the program is needed , for example ： Get rid of Debug Stage debugging means .
• Divide into Debug/Release The version is not C/C++ Characteristics of language ; No matter what language the program is written in, it has these two stages , Therefore, they all need to be distinguished , But other languages （ for example ：java etc. ） The requirements for performance are relatively low, and the compilation and operation mechanism is similar to C/C++ Different languages and better dynamics （ Debugging methods such as logs can be dynamically set at runtime ） therefore Debug/Release The partition requirements of the version are not like C/C++ So obvious .
• Debug/Release Versioning is not a specific method , It is a policy that can be customized ; There are no regulations Debug and Release What should the version do , What should not be done , Nor is there a specific option to cover it Debug/Release Division of versions , Compiler options and usage IDE You can generate versions with debugging information , That's language level Debug/Release Versioning , You also need to have a business layer Debug/Release Versioning , for example ：Debug/Release Different stages Log Output .

strip and Release The difference between

• A program that will be accompanied by debugging information strip Not equivalent to Release edition , Compiler plus -g The program compiled with the compile option will have its own debugging information ,strip The program will remove the debugging information and symbol table of the program , Although binary programs are generated in two ways strip The file size is the same after , But what is generated is language level Release edition , Business level debugging tools still exist , for example ： Assertion , Self added debugging means , And these means （ Assertion ） The existence of is very dangerous .

C/C++ How to divide when programming Debug/Release edition

• Use NDEBUG macro , The macro is not defined by default , Corresponding Debug edition , Generate Release version , You need to define the macro manually , This macro can also control system level debugging methods such as assertions .
• The way is C/C++ The conventional division of the project , Many system codes and open source projects adopt this method , Therefore, the macro can be judged in the code NDEBUG Whether it exists or not Release Mode or Debug Pattern , Or expand , for example ：

#ifndef NDEBUG
    std::cout << "Debug Mode" << std::endl;
#else
    std::cout << "Release Mode" << std::endl;
#endif