Does anyone know how I can for the g++ or gcc runtime to scramble the ram where an object was after delete? I have a theory that I’m using an object after it has been deleted but in practice it rarely crashes.
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.
Does anyone know how I can for the g++ or gcc runtime to scramble the ram where an object was after delete? I have a theory that I’m using an object after it has been deleted but in practice it rarely crashes.
inline void operator delete(void* memblock) { //you custom stuff }would override the global. I used to use this for security so that we could zero out the memory so its less likely to leak important information.