How does free know how much to free?

by

When you call malloc(), you specify the amount of memory to allocate. The amount of memory actually used is slightly more than this, and includes extra information that records (at least) how big the block is. You can’t (reliably) access that other information – and nor should you :-).

When you call free(), it simply looks at the extra information to find out how big the block is.

More Related Contents:

  1. Does free(ptr) where ptr is NULL corrupt memory?
  2. C pointers : pointing to an array of fixed size
  3. Is the compiler allowed to recycle freed pointer variables?
  4. Should one really set pointers to `NULL` after freeing them?
  5. C – Accessing data AFTER memory has been free()ed?
  6. How are we able to access the pointer after deallocating the memory?
  7. How to check if a pointer is freed already in C?
  8. C array pointer increment
  9. Convert double * to double [9] in C [closed]
  10. Why this program is crashing?
  11. Segmentation fault using scanf() [closed]
  12. Is an array name a pointer?
  13. How do you pass a function as a parameter in C?
  14. How can I get the size of an array from a pointer in C?
  15. Should I explicitly cast malloc()’s return value? [duplicate]
  16. In C, can a const variable be modified via a pointer?
  17. Pointers as function arguments in C
  18. What is the result of NULL + int?
  19. free char*: invalid next size (fast) [duplicate]
  20. Difference between char* var; and char *var;? [duplicate]
  21. Rationale behind the container_of macro in linux/list.h
  22. casting char[][] to char** causes segfault?
  23. Literal string initializer for a character array
  24. Simple swap function…why doesn’t this one swap?
  25. C isn’t that hard: void ( *( *f[] ) () ) ()
  26. When printf is an address of a variable, why use void*?
  27. free a double pointer
  28. What happens to memory after free()?
  29. Why is the size of a function in C always 1 byte?
  30. What does this C statement mean?

Leave a Comment