This is by far the most frequent single cause for different behaviour between debug and release builds, so chances are good that this fixes your problem (and for the future, remember to always initialize your variables). The reason why the debug build seemed to work is that the debug version of the runtime library initializes dynamic memory and stack variables to known values (in order to track down memory allocation and overwrite errors), while the release version of the runtime library doesn't. And if you go back and see where the value of that variable is set, you will most probably find out that it isn't: You simply forgot to initialize that variable. When debugging your release build this way, you will probably discover that at a certain point during execution, a variable has a different value in the release and in the debug build, causing the differing behaviour. This shouldn't be a concern, if it is, turn off optimizations.
VISUAL STUDIO DEBUG NOT WORKING C PROGRAM CODE
Note however, that due to optimizations turned on in the release build, the instruction pointer will sometimes be off by a few code lines, or even skip lines altogether (as the optimizer didn't generate code for them). Regardless of whether your program crashes or just doesn't behave as expected, running it in the debugger will show you why. If you rebuild your project now, you will be able to run it in the debugger. Then go to the tab 'Linker', and turn on 'Generate Debug Info'. Just go to 'Project -> Settings', choose the Win32 Release configuration, tab 'C/C++', 'General' and set 'Debug Info' to 'Program Database'. Now, what's the first implication of all this? That, as opposed to a common misunderstanding, you can debug a release build. There are a few other differences, but these are the most important ones.
Various compiler optimizations turned on.Release version of the runtime libraries is used.Subdirectory 'Release' used for temporary and output files.Debug version of the runtime libraries is used.Subdirectory 'Debug' used for temporary and output files.Now let's see what the two default configurations typically include and what distinguishes them: Actually, you can modify those configurations, delete them, or create new ones. These are just convenient starter configurations with several preset options which are suitable for typical debug builds or release builds respectively, but you are by no means restricted to those settings. The VC++ IDE offers the possibility to define configurations which include a set of project settings (like compiler / linker options, output directories etc.) When a project is created using AppWizard, you get two default configurations: "Win32 Debug" and "Win32 Release". Q: Why does program work in debug mode, but fail in release mode?Ī: First of all, there is no such thing as 'debug mode' or 'release mode'.
0 kommentar(er)
