Where exactly does C++ standard say dereferencing an uninitialized pointer is undefined behavior?

by

Section 4.1 looks like a candidate (emphasis mine):

An lvalue (3.10) of a
non-function, non-array type T can be
converted to an rvalue. If T is an
incomplete type, a program that
necessitates this conversion is
ill-formed. If the object to which the
lvalue refers is not an object of type
T and is not an object of a type
derived from T, or if the object is
uninitialized, a program that
necessitates this conversion has
undefined behavior. If T is a
non-class type, the type of the rvalue
is the cv-unqualified version of T.
Otherwise, the type of the rvalue is
T.

I’m sure just searching on “uninitial” in the spec can find you more candidates.

More Related Contents:

  1. Accessing inactive union member and undefined behavior?
  2. When does invoking a member function on a null instance result in undefined behavior?
  3. Has C++ standard changed with respect to the use of indeterminate values and undefined behavior in C++14?
  4. Take the address of a one-past-the-end array element via subscript: legal by the C++ Standard or not?
  5. Optimizing away a “while(1);” in C++0x
  6. Does initialization entail lvalue-to-rvalue conversion? Is `int x = x;` UB?
  7. Do I need to cast to unsigned char before calling toupper(), tolower(), et al.?
  8. Is `reinterpret_cast`ing between hardware SIMD vector pointer and the corresponding type an undefined behavior?
  9. Why does left shift operation invoke Undefined Behaviour when the left side operand has negative value?
  10. Does “Undefined Behavior” really permit *anything* to happen? [duplicate]
  11. Difference between Undefined Behavior and Ill-formed, no diagnostic message required
  12. Is `long` guaranteed to be at least 32 bits?
  13. Is right shift undefined behavior if the count is larger than the width of the type?
  14. Is passing a C++ object into its own constructor legal?
  15. Are multiple mutations of the same variable within initializer lists undefined behavior pre C++11
  16. Does not evaluating the expression to which sizeof is applied make it legal to dereference a null or invalid pointer inside sizeof in C++?
  17. In C++11, does `i += ++i + 1` exhibit undefined behavior?
  18. So why is i = ++i + 1 well-defined in C++11?
  19. Why is f(i = -1, i = -1) undefined behavior?
  20. Implementing a std::vector like container without undefined behavior
  21. Are pointer variables just integers with some operators or are they “symbolic”?
  22. The behaviour of floating point division by zero
  23. Can branches with undefined behavior be assumed unreachable and optimized as dead code?
  24. Dangling references and undefined behavior
  25. In which versions of the C++ standard does “(i+=10)+=10” have undefined behaviour?
  26. Observable behavior and undefined behavior — What happens if I don’t call a destructor?
  27. Can we apply content not explicitly cited from the normative references to the C++ standard?
  28. Is segmentation fault actual undefined behavior when we refer to a non-static data-member
  29. Why does integer overflow on x86 with GCC cause an infinite loop?
  30. Is the order of iterating through std::map known (and guaranteed by the standard)?

Leave a Comment