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’m getting
*** glibc detected *** (/my/program/…): malloc(): memory corruption: 0xf28000fa ***
I’ve run under valgrind, which reports cases of reading memory that has been freed, but no cases of illegal memory writes.
Could reading freed memory cause memory corruption? If not, any suggestions where else to look beyond the valgrind output?
You can use GDB to watch each write in this memory address, like this:
Then you can debug where the problem is.
Reading doesn’t cause memory corruption, but there are a lot of situations that you don’t even imagine that could be the cause of this, and Valgrind is not a perfect tool.
See more information about debugging memory issues here.