Quote:
Originally Posted by Dinarchik
*** glibc detected *** /home/din/Projects/new-daProject/Debug/manager: malloc(): memory corruption: 0x0b16fcc0 ***
|
The point in your program where the problem is detected and reported is not where the problem actually occurred (so the Backtrace you quoted would be useless even with the source code pointed to be that Backtrace).
I'm not sure exactly what the 0x0b16fcc0 points to. I think it is the address of a corrupted location. You can run the program in gdb and tell it to break on every write to that location. If it is the corrupted location, that would break when malloc uses that location, then break again when the bug in your code corrupts the location that should still belong to malloc.
Most likely your code malloc'ed some other object earlier and then used more than the full size of that other object. That corrupted data structures after that object that malloc needs in order to handle a later allocation.