Stack Break Release For Free

In order to debug programs with functions (i.e. most programs), it is helpful to inspect the variables of all functions in the current call stack, i.e. the functions called to get to the current point in the program. GDB can only directly inspect local variables of the current function.

For example, if a function is simple and only called once, the compiler can inline the function in release mode. Debug mode doesn't have these kind of optimization and is designed for debugging your code. You can then put a breakpoint on that int declaration line, and it'll be hit, even in release mode.

You can debug a release build of an application.

Visual Studio projects have separate release and debug configurations for your program. You build the debug version for debugging and the release version for the final release distribution. In debug configuration, your program compiles with full symbolic debug information and no optimization.

The difference is the compiler settings. Release is much more optimized, resulting in faster and smaller code, but is harder to debug since some source code statements may be removed/rearranged. Variables may be optimized out entirely. I would use Debug exclusively unless performance becomes an issue.

Visually trace the call stack In Visual Studio Enterprise (only), you can view code maps for the call stack while debugging. In the Call Stack window, open the shortcut menu. Choose Show Call Stack on Code Map (Ctrl + Shift + `).

To debug a release build Open the Property Pages dialog box for the project. For details, see Set C++ compiler and build properties in Visual Studio. Click the C/C++ node. ... Expand Linker and click the General node. ... Select the Debugging node. ... Select the Optimization node. ... You can now debug your release build application.