Malloc and array index confusion in C

by

C doesn’t enforce any array bounds checking, so while you requested space for 5 integers, you used more.

In fact you overwrote 4 memory locations that really weren’t set aside for your specific purpose. Your program went past the area in memory that was set aside for your array, and started to store values in memory outside the allocated region.

The fact that this “worked” is just pure luck and not something to be dependent on. It may work the next 100 times, or it may fail the next time you try it, with most likely a “segmentation fault” message.

Defensive programming, like you did by sensibly checking the return value of malloc, being mindful that you are responsible for bounds checking, compiling code with high warning levels enabled, etc are some of your best defenses to guard against these sort of errors. Other tools, such as valgrind, lint type checkers can also help, but at the end it’s up to you.

One of C’s greatest strengths, its freedom to do all sorts of things, low and high-level, is also one of its greatest weaknesses IMO. If Java is a Volvo, C is perhaps more like a Ferrari with spotty breaks at times 🙂

More Related Contents:

  1. Using malloc for allocation of multi-dimensional arrays with different row lengths
  2. Difference between array type and array allocated with malloc
  3. Freaky way of allocating two-dimensional array?
  4. How to use realloc in a function in C
  5. Dynamically create an array of strings with malloc
  6. Find malloc() array length in C? [duplicate]
  7. Getting the size of a malloc only with the returned pointer
  8. Variable Sized Arrays vs calloc in C
  9. C programming: array not have any bound [duplicate]
  10. How to resolve a variable for char length? [closed]
  11. C pointer to array/array of pointers disambiguation
  12. What REALLY happens when you don’t free after malloc before program termination?
  13. Difference between passing array and array pointer into function in C
  14. Create a pointer to two-dimensional array
  15. Dynamic allocation of an unknown matrix in C
  16. Setting variable to NULL after free
  17. typedef fixed length array
  18. “error: assignment to expression with array type error” when I assign a struct field (C)
  19. Why do I get a C malloc assertion failure?
  20. Is this a pointer to a pointer of the start of an array?
  21. Should I check if malloc() was successful?
  22. Is `*((*(&array + 1)) – 1)` safe to use to get the last element of an automatic array?
  23. Why do you specify the size when using malloc in C?
  24. size of array in c
  25. Why can´t we assign a new string to an char array, but to a pointer?
  26. Segmentation Fault While Creating Large Arrays in C
  27. C: Correctly freeing memory of a multi-dimensional array
  28. Strange character after an array of characters
  29. “int *nums = {5, 2, 1, 4}” causes a segmentation fault
  30. Why exactly should I not call free() on variables not allocated by malloc()?

Leave a Comment