Uninitialized pointers in code

by 
int* ptr = NULL; //Is this going to avoid the problem

This will cause ptr to point to NULL which you can explicitly check for as a default/uninitialized value. It prevents the problem you describe, but a careless programmer can still accidentally dereference a null pointer without checking, causing undefined behaviour.

The main advantage is your convenience for checking whether the ptr has or has not been initialized to anything, ie:

 if (ptr != NULL)
 {
     // assume it points to something
 }

Since this is pretty idiomatic, its pretty dangerous to not initialize the pointer to NULL. The pointer would be initialized to a non-NULL garbage value that doesn’t really point to anything real. Worst of all, the check above would pass, causing even worse problems if it just so happens that the address in the pointer is memory you can legally access. In some Embedded environments, you might be able to access any part of memory, so you might accidentally corrupt random parts of memory or random parts of your executing code.

More Related Contents:

  1. Is it safe to delete a NULL pointer?
  2. Can I use if (pointer) instead of if (pointer != NULL)?
  3. What is a void pointer and what is a null pointer?
  4. How to deal with c-string pointers [closed]
  5. Is segmentation fault actual undefined behavior when we refer to a non-static data-member
  6. Return array in a function
  7. Are arrays Pointers? [duplicate]
  8. Are there benefits of passing by pointer over passing by reference in C++?
  9. NULL vs nullptr (Why was it replaced?) [duplicate]
  10. What can I use instead of the arrow operator, `->`?
  11. How to avoid memory leaks when using a vector of pointers to dynamically allocated objects in C++?
  12. Determine the size of a C++ array programmatically?
  13. What is the ‘this’ pointer?
  14. difference between a pointer and reference parameter?
  15. C++ Is it possible to determine whether a pointer points to a valid object?
  16. Pointers in c++ after delete
  17. How are iterators and pointers related?
  18. What is the purpose of allocating a specific amount of memory for arrays in C++?
  19. How to know if a pointer points to the heap or the stack?
  20. C++: Is it safe to cast pointer to int and later back to pointer again?
  21. Could I ever want to access the address zero?
  22. How to make an array with a dynamic size? General usage of dynamic arrays (maybe pointers too)? [closed]
  23. Dereferencing deleted pointers always result in an Access Violation?
  24. Difference between const. pointer and reference?
  25. Function returning array but main showing garbage [duplicate]
  26. C++: difference between ampersand “&” and asterisk “*” in function/method declaration?
  27. dereferencing a pointer when passing by reference
  28. difference between pointer to an array and pointer to the first element of an array
  29. What happen to pointers when vectors need more memory and realocate memory?
  30. int *array = new int[n]; what is this function actually doing?

Leave a Comment