Why is out-of-bounds pointer arithmetic undefined behaviour?

by

That’s because pointers don’t behave like integers. It’s undefined behavior because the standard says so.

On most platforms however (if not all), you won’t get a crash or run into dubious behavior if you don’t dereference the array. But then, if you don’t dereference it, what’s the point of doing the addition?

That said, note that an expression going one over the end of an array is technically 100% “correct” and guaranteed not to crash per §5.7 ¶5 of the C++11 spec. However, the result of that expression is unspecified (just guaranteed not to be an overflow); while any other expression going more than one past the array bounds is explicitly undefined behavior.

Note: That does not mean it is safe to read and write from an over-by-one offset. You likely will be editing data that does not belong to that array, and will cause state/memory corruption. You just won’t cause an overflow exception.

My guess is that it’s like that because it’s not only dereferencing that’s wrong. Also pointer arithmetics, comparing pointers, etc. So it’s just easier to say don’t do this instead of enumerating the situations where it can be dangerous.

More Related Contents:

  1. Undefined, unspecified and implementation-defined behavior
  2. Is segmentation fault actual undefined behavior when we refer to a non-static data-member
  3. C++ delete – It deletes my objects but I can still access the data?
  4. Is signed integer overflow still undefined behavior in C++?
  5. Uninitialized variable behaviour in C++
  6. Is uninitialized local variable the fastest random number generator?
  7. Does the C++ standard allow for an uninitialized bool to crash a program?
  8. Detecting signed overflow in C/C++
  9. Multithreading program stuck in optimized mode but runs normally in -O0
  10. Why does this loop produce “warning: iteration 3u invokes undefined behavior” and output more than 4 lines?
  11. Why does integer overflow on x86 with GCC cause an infinite loop?
  12. Difference between Undefined Behavior and Ill-formed, no diagnostic message required
  13. C++ compilation bug?
  14. Why is initialization of a new variable by itself valid? [duplicate]
  15. Is this infinite recursion UB?
  16. Does the ‘offsetof’ macro from invoke undefined behaviour?
  17. Are multiple mutations of the same variable within initializer lists undefined behavior pre C++11
  18. Access array beyond the limit in C and C++ [duplicate]
  19. Division by zero: Undefined Behavior or Implementation Defined in C and/or C++?
  20. So why is i = ++i + 1 well-defined in C++11?
  21. Program behaving strangely on online IDEs
  22. Implementing a std::vector like container without undefined behavior
  23. new() without delete() is Undefined Behavior or merely Memory Leak? [duplicate]
  24. Why does printf(“%f”,0); give undefined behavior?
  25. Is left and right shifting negative integers defined behavior?
  26. At what point does dereferencing the null pointer become undefined behavior?
  27. When a float variable goes out of the float limits, what happens?
  28. Can different GCC dialects be linked together?
  29. Dangling references and undefined behavior
  30. Can undefined behavior erase the hard drive?

Leave a Comment