Behaviour of malloc with delete in C++

c++ malloc delete-operator
Luv picture Luv · Jun 1, 2012 · Viewed 28.4k times · Source 
int *p=(int * )malloc(sizeof(int));

delete p;

When we allocate memory using malloc then we should release it using free and when we allocate using new in C++ then we should release it using delete.

But if we allocate memory using malloc and then use delete, then there should be some error. But in the above code there's no error or warning coming in C++.

Also if we reverse and allocate using new and release using free, then also there's no error or warning.

Why is it so?

Answer

Cat Plus Plus picture Cat Plus Plus · Jun 1, 2012

This is undefined behaviour, as there's no way to reliably prove that memory behind the pointer was allocated correctly (i.e. by new for delete or new[] for delete[]). It's your job to ensure things like that don't happen. It's simple when you use right tools, namely smart pointers. Whenever you say delete, you're doing it wrong.

Related questions

In what cases do I use malloc and/or new?

I see in C++ there are multiple ways to allocate and free data and I understand that when you call malloc you should call free and when you use the new operator you should pair with delete and it is …

Read More
How do malloc() and free() work?

I want to know how malloc and free work. int main() { unsigned char *p = (unsigned char*)malloc(4*sizeof(unsigned char)); memset(p,0,4); strcpy((char*)p,"abcdabcd"); // **deliberately storing 8bytes** cout << p; free(p); // Obvious Crash, but I need …

Read More
invalid conversion from `void*' to `char*' when using malloc?

I'm having trouble with the code below with the error on line 5: error: invalid conversion from void* to char* I'm using g++ with codeblocks and I tried to compile this file as a cpp file. Does it matter? #include <…

Read More