<div>
You have to match the allocation with deallocation<br />
<br />
malloc/free<br />
new/delete<br />
new []/ delete []<br />
<br />

</div>


You have to match the allocation with deallocation

malloc/free
new/delete
new []/ delete []



<div>
This will be a more help to you.<br />
<br />
<a href="http://blogs.msdn.com/oldnewthing/archive/2004/02/04/67384.aspx" rel="ugc">http://blogs.msdn.com/oldnewthing/archive/2004/02/04/67384.aspx</a>
</div>


This will be a more help to you.

http://blogs.msdn.com/oldnewthing/archive/2004/02/04/67384.aspx [http://blogs.msdn.com/oldnewthing/archive/2004/02/04/67384.aspx]

<div>
Well thats the thing; isn't new and delete matching? If I match the allocation/deallocation routines with a new and delete; heap corruption still occurs<br />
<br />
Note if I comment out the code in between the new and delete call it works; I'm just curious as to what happens internally as a result of the code in between? How does that code result in the delete complaining about heap corruption?
</div>


Well thats the thing; isn't new and delete matching? If I match the allocation/deallocation routines with a new and delete; heap corruption still occurs

Note if I comment out the code in between the new and delete call it works; I'm just curious as to what happens internally as a result of the code in between? How does that code result in the delete complaining about heap corruption?

<div>
thanks that was what I was looking for (got mixed up with malloc where you specify the size). Yes it should be in c++ :)
</div>


thanks that was what I was looking for (got mixed up with malloc where you specify the size). Yes it should be in c++ :)

<div>
<div class="content wysiwyg-content">
Why does the following result in heap corruption<br />
char* tempString = new char(strLen+1)<br />
for( i = 0; i &lt;&nbsp;strLen; i++)<br />
{<br />
&nbsp; &nbsp; *(tempString+1) = 'A';<br />
} <br />
tempString[srcLen] = NULL; &nbsp; &nbsp; <br />
delete tempString &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;// Heap Corruption with delete []tempString<br />
<br />
<br />
If i replace the allocation line with<br />
char* tempString = new char [strLen + 1];<br />
it works? why?
</div>
</div>


Why does the following result in heap corruption
char* tempString = new char(strLen+1)
for( i = 0; i < strLen; i++)
{
    *(tempString+1) = 'A';
} 
tempString[srcLen] = NULL;     
delete tempString                      // Heap Corruption with delete []tempString


If i replace the allocation line with
char* tempString = new char [strLen + 1];
it works? why?

Heap Corruption with delete

C is a general-purpose, imperative computer programming language, supporting structured programming, lexical variable scope and recursion, while a static type system prevents many unintended operations. By design, C provides constructs that map efficiently to typical machine instructions, so it has found lasting use in applications that had formerly been coded in assembly language, including operating systems as well as various application software for computers ranging from supercomputers to embedded systems. It is distinct from C++ (which has its roots in C) and C#, and many later languages have borrowed directly or indirectly from C.