Question

From here: http://google-glog.googlecode.com/svn/trunk/doc/glog.html

Debug Mode Support
Special “debug mode” logging macros only have an effect in debug mode and are compiled away to nothing for non-debug mode compiles.

What does “debug mode” mean w.r.t C++ program?

Can we say a program is in debug mode when we are using GDB on it?

Answer 1

There’s three sides to “debug mode”.

A lot of libraries (including standard libraries) will insert debug-helping code (array bounds checking, invariant assertions, that sort of thing) when they are compiled in debug mode. They remove these checks in production/non-debug mode to help performance.

Compilers have debug switches. The set debug macros that the libraries use to detect whether you are compiling for debug or not, and insert debug symbols in the produced binaries. This helps debuggers make the link between the binary code that is running and the source code that generated it.

Running an program in a debugger is a “runtime debug mode”. You can run an executable in a debugger whether or not it was built for debugging. You’ll get more information with a debug build.

All three of these “debug modes” are independent. You could (usually) compile library debug checks in a production build by setting the appropriate macros/defines manually without asking the compiler to output debug symbols.

None of this is specific to C++ (or C). A lot of other languages have these concepts.