Let’s say I prefer debugging a release build of my software during development.
What problems might I miss by doing that?
Let’s say I prefer debugging a release build of my software during development. What
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Let’s say I prefer debugging a release build of my software during development.
What problems might I miss by doing that?
You may miss buffer overruns. The debug code adds padding around the memory available to your program, the release build does not. So the debugger can detect and warn when you write unowned memory in the debug build. In the release build the same problem may go unnoticed until the user enters that one special input that crashes everything.
The same is true of using uninitialized variables. The debug build detects it, the release build will not. And it’s Murphy’s Law that the last change before release will change the uninitialized variable to something that causes problems with the section you decided not to retest.