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.
Are there tools to catches deletion of a stack object, how likely that gcc and Visual Studio debug build will break on that event immediately?
I deal with big, old projects, so that is not a question on how to write code, but how to detect and fix problems.
Most of the heap implementations are not tolerate to invalid pointers (i.e. when you
deletean address which was not returned to you by the heap). Almost for sure standard windows heap, and CRT’s heap (implemented by MSVC) cause a debug breakpoint in such a case.You may also replace the implementation of
new/deleteoperators and do the checking yourself (in your case you only want to check if the address belongs to the stack memory, which is easy).