In many cases, code which works in the debug version doesn’t work normally in the release version. I always encounter these questions, just like the earthquake happening. Which Big Beer can help me to give some thought??
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.
In many cases, code which works in the debug version doesn’t work normally in the release version. I always encounter these questions, just like the earthquake happening. Which Big Beer can help me to give some thought??
Generally if an app works in debug but not in release it’s because some variable or memory wasn’t properly set to an initial value.
In debug builds variables and memory are generally set to zero but in release this step is skipped to save time. Extra data is also added around objects and allocated memory as barriers to detect memory overwrites.
Sometimes (very rarely) an optimization in release build introduces an error