I keep getting this error after my application is running for 2 days.
I’ve been told it’s been some kind of buffer overflow, but is it the only option?
The app is written in C++ using Visual C++ 6.0.
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.
I keep getting this error after my application is running for 2 days.
I’ve been told it’s been some kind of buffer overflow, but is it the only option?
The app is written in C++ using Visual C++ 6.0.
In debug, when you get dynamic buffer by
new, a special code gets inserted before and after the buffer to guard the buffer.Ex:
If you overrun the buffer, the guard inserted gets corrupted and when you try to delete the buffer, then debugger would assert after detecting buffer overrun.
Its bit difficult to find the buffer overrun in large code base. I would suggest couple of ways which can help you to detect this scenario:
Its good tool to detect memory corruption.
enabled:
Refer my answer to similar question here