Re: Bug in MFC CList?
On Sun, 22 Jul 2007 23:12:02 -0700, Dani <Dani@discussions.microsoft.com>
wrote:
Hello there!
I have just noticed a bug in MFC, in the CList class.
To make sure there are no unexpected memory leaks,
Just create a new clean MFC solution, and write the following, somewhere...:
CList<int> * lstBuggy = new CList<int>[5];
delete lstBuggy; // Exception thrown - Corrupted Heap!!!
Something is going wrong when dynamically allocating an array of CList...
I'm working with VS2005 SP1, if somebody out there can test this code with
other version of VS, it'll be great...
No need. You are using scalar-delete with array-new, which is undefined.
You must always match allocation and deallocation methods, which means
matching up new/delete, new[]/delete[], malloc/calloc/realloc/free, etc.
Of course, you should simply be using:
CList<int> lstBuggy[5];
If you truly need to dynamically allocate it, you should use a container
class such as std::vector, and then you don't have to worry about deleting
the CList array. In general, if you're using delete on a regular basis, you
aren't using C++ effectively. You should be using smart pointer classes
such as std::auto_ptr and boost::shared_ptr for scalars and container
classes such as std::vector for arrays.
--
Doug Harrison
Visual C++ MVP