Thread: Dynamic memory ... how is this producing Debug assertions in Visual Studio

Well, ok ... not sure what is going on here with this rather innocuous code:

Code:

int main(bleh blah){
	int *p(new int(124));
	int *q = new int(40);
	int *r = p;
	p = q;
	cout << *r << endl;
	delete p; delete q;
	p = q = r = nullptr;

        return whatever
}

All I am doing is dynamically assigning memory and then deleting it. r is set to a nullptr along with p and q. This is producing debug assertion problems in Visual Studio.

I am already acquainted with smart pointers such as shared_ptr, unique_ptr, and weak_ptr so I am simply exploring managing dynamic memory myself.

Originally Posted by whiteflags

... is cute, then you won't get good help.

My apologies ... not trying to be cute but rather terse as the parameters to main and what it returns are irrelevant to the question. I believe I have also figured it out.

Code:

int main(int argc, char *argv[]){
	int *p(new int(124));
	int *q = new int(40);
	int *r = p;
	delete p;
	p = q;
	r = q;
	cout << *r << endl;
	delete q;
	p = q = r = nullptr;

	return EXIT_SUCCESS;
}

A pointer had gone invalid somewhere in the previous example.

int *p(new int(124));
int *q = new int(40);
int *r = p;
p = q;

The memory stored at location p is leaked after this point. Your problem showed up when you deleted the same region twice.

delete p; delete q;

p and q were the same.