25 Jan
2010
25 Jan
'10
6:07 p.m.
Igor R wrote:
Wikipedia says that 0xFEEEFEEE is "Used by Microsoft's HeapFree() to mark freed heap memory".
Yes, and it's a begining of 72 bytes block of feeefeee. Apparently, it means that out_buffer.data was already freed. But I can't realize how it can be...
Is it possible that the free does not fail for the functor itself but for a member variable (for instance a pointer which is freed in the destructor)?