Let’s look at the first two lines of your code: str = (char *) malloc(15); strcpy(str, “63tczfqV4nqB2YnH9iFJbGvGyyDkvK341rrj0G0mo1PEYniOVHejVIFIQnJzHSSMRbuyGMCZ4M5HFMV4y1q4QgYqyxp2XkTjxaolKTkaw1r25S2Emz061tw1”); At this point, you have broken the rules of the C language. strcpy will write past the end of str which causes undefined behavior. Everything that happens after this point is kinda up in the air. 5 solved … Read more
Can I install glibc from some repo? Not likely: distributions usually don’t ever update the major/minor version of glibc from the one they originally shipped with, because the likelihood of breaking applications is too great. You may have to build glibc-2.15, or better current glibc-2.24 from source and install it into non-default location. See this … Read more
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 … Read more