No I just wanted to know about it... I have not tried to delete the getbuffer allocated memory.
In my code the debug error is thrown once the destructor frees all the memories and finally calls an instruction
call operator delete (00504440)
This instruction generally gets executed whenever a destructor is called in all programs. Merely it is an inbuilt call at the end of destructor call...
and in debug window I Get
memory check error at 0x0803CD3C = 0x14, should be 0xFD.
memory check error at 0x0803CD3D = 0xCB, should be 0xFD.
memory check error at 0x0803CD3E = 0x4C, should be 0xFD.
memory check error at 0x0803CD3F = 0x5F, should be 0xFD.
Ok. First, just to verify that this is where the problem comes from, try commenting out delete m_temp1; and delete m_temp2; and see what happens. Then, if these
two are indeed the cause of the problem, it would help a lot if you showed us the parts
of the code that involve m_temp1 , m_temp2 , m_HOBuffer and m_pBuffer .
I found the error... in the declaration part one of the CString variable was declared and it was not used in any part of the code... when the destructor tried to delete that cstring variable it threw a debug assertion error... that CString variable was removed and the application debugged fine...