What does ‘corrupted double-linked list’ mean

I have found the answer to my question myself:)

So what I didn’t understand was how the glibc could differentiate between a Segfault and a corrupted double-linked list, because according to my understanding, from perspective of glibc they should look like the same thing. Because if I implement a double-linked list inside my program, how could the glibc possibly know that this is a double-linked list, instead of any other struct? It probably can’t, so thats why i was confused.

Now I’ve looked at malloc/malloc.c inside the glibc’s code, and I see the following:

1543 /* Take a chunk off a bin list */
1544 #define unlink(P, BK, FD) {                                            \
1545   FD = P->fd;                                                          \
1546   BK = P->bk;                                                          \
1547   if (__builtin_expect (FD->bk != P || BK->fd != P, 0))                \
1548     malloc_printerr (check_action, "corrupted double-linked list", P); \
1549   else {                                                               \
1550     FD->bk = BK;                                                       \
1551     BK->fd = FD;                                                       \

So now this suddenly makes sense. The reason why glibc can know that this is a double-linked list is because the list is part of glibc itself. I’ve been confused because I thought glibc can somehow detect that some programming is building a double-linked list, which I wouldn’t understand how that works. But if this double-linked list that it is talking about, is part of glibc itself, of course it can know it’s a double-linked list.

I still don’t know what has triggered this error. But at least I understand the difference between corrupted double-linked list and a Segfault, and how the glibc can know this struct is supposed to be a double-linked list:)

Related Posts:

  1. How to deal with bad_alloc in C++?
  2. malloc for struct and pointer in C
  3. delete vs delete[] operators in C++
  4. How to solve access violation writing location error?
  5. Calculating Page Table Size
  6. Is “delete this” allowed in C++?
  7. What and where are the stack and heap?
  8. What are the -Xms and -Xmx parameters when starting JVM?
  9. What does pss mean in /proc/pid/smaps
  10. What is the array form of ‘delete’?
  11. How can I explicitly free memory in Python?
  12. Is there a way to delete created variables, functions, etc from the memory of the interpreter?
  13. Understanding “corrupted size vs. prev_size” glibc error
  14. Which Python memory profiler is recommended? [closed]
  15. Oracle startup not possible – ORA-00845: MEMORY_TARGET not supported on this system – but memory size seems to be fine
  16. Deleting a dynamically allocated 2D array
  17. Thread 1: EXC_BAD_ACCESS (code=1, address=0x0) standard C memory issue
  18. RHEL 6 – how to install ‘GLIBC_2.14’ or ‘GLIBC_2.15’?
  19. How do malloc() and free() work?
  20. Deleting an object in C++
  21. What are the differences between virtual memory and physical memory?
  22. Conflict Miss v/s Compulsory Miss
  23. Valgrind complains with “Invalid write of size 8”
  24. How to delete object?
  25. How do I determine the size of an object in Python?
  26. I get this error: “glibc detected”
  27. What does this GCC error “… relocation truncated to fit…” mean?
  28. malloc(): memory corruption
  29. C: pointer to array of pointers to structures (allocation/deallocation issues)
  30. Why is this vector iterator not incrementable?
  31. Should I set a MaxMetaspaceSize?
  32. Dynamic vs static array in c
  33. Releasing memory in Python
  34. /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
  35. calculate the effective access time
  36. Different ways to deallocate an array – c++
  37. How to force JavaScript to deep copy a string?
  38. How can I create a dynamically sized array of structs?

Leave a Comment