[Solved] I do not know ‘glibc detected’ in C

Question

It means you have heap corruption in your program. You likely allocate some memory using malloc, but write outside the actual bounds, corrupting the heap. When you call free, glibc detects the corruption and reports it (specifically, the size of the next free chunk is overwritten).

You should definitely fix this problem. Valgrind can be a huge help in tracking down the code that actually causes the heap corruption.

Accepted Answer

It means you have heap corruption in your program. You likely allocate some memory using malloc, but write outside the actual bounds, corrupting the heap. When you call free, glibc detects the corruption and reports it (specifically, the size of the next free chunk is overwritten).

You should definitely fix this problem. Valgrind can be a huge help in tracking down the code that actually causes the heap corruption.