How serious is the new/delete operator mismatch error?

by

It’s undefined behavior serious (it could work, it could crash, it could do something else).

More Related Contents:

  1. Is “delete this” allowed in C++?
  2. How should I write ISO C++ Standard conformant custom new and delete operators?
  3. How does delete[] know it’s an array?
  4. How do you ‘realloc’ in C++?
  5. Why would one replace default new and delete operators?
  6. overloading new/delete
  7. delete[] an array of objects
  8. When to use new and delete
  9. Why there is no placement delete expression in C++?
  10. Why doesn’t delete destroy anything?
  11. C++ delete – It deletes my objects but I can still access the data?
  12. In what cases do I use malloc and/or new?
  13. delete vs delete[] operators in C++
  14. Is it safe to delete a NULL pointer?
  15. Calling delete on variable allocated on the stack
  16. delete vs delete[] [duplicate]
  17. Why doesn’t delete set the pointer to NULL?
  18. placement new and delete
  19. Is it still safe to delete nullptr in c++0x?
  20. Is the pointer guaranteed to preserve its value after `delete` in C++?
  21. Deleting a pointer in C++
  22. What are uses of the C++ construct “placement new”?
  23. Does new[] call default constructor in C++?
  24. new() without delete() is Undefined Behavior or merely Memory Leak? [duplicate]
  25. What does “new int(100)” do?
  26. Must new always be followed by delete? [duplicate]
  27. Call destructor and then constructor (resetting an object)
  28. Will new operator return NULL? [duplicate]
  29. Calling delete on NULL pointers – C++03 vs C++11
  30. Is the whole object freed with a non-virtual destructor and a Base class pointer?

Leave a Comment