Hi everyone,
Just a quick question which I couldn't find through googling. Does
*** glibc detected *** ./a.out: malloc(): memory corruption: 0x00000000010a6360
mean that memory location is no longer usable and that I have a memory leak??
Also does running programs in valgrind protect against memory leaks? I refrain from using valgrind because sometimes my program works while using it but doesnt if I just use a normal terminal.
> *** glibc detected *** ./a.out: malloc(): memory corruption: 0x00000000010a6360
> mean that memory location is no longer usable and that I have a memory leak??
No, it means you trashed memory you don't own.
> Also does running programs in valgrind protect against memory leaks?
No, valgrind is a diagnostic tool to help you find things like buffer overruns and memory leaks.
> I refrain from using valgrind because sometimes my program works while using it but doesnt if I just use a normal
But does valgrind spit out a whole bunch of messages when it's "working" in valgrind, but not working normally?
If you're seeing valgrind messages, you need to be fixing the code.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
