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.
according to MSDN, Visual Studio uses a special heap in debug mode that has extra “no man’s land” bytes set to 0xFD by default to track heap corruption
Is there a way to force visual to break when such values are overwritten? I can’t find this information anywhere and it seems extremely useful, much more than having to manually dump the memstat like MSDN proposes
thanks
You could try using
_CrtSetDbgFlag()when in debug mode.Reference.