Re: memory leak detection techniques
Hi Dave,
"David Webber" <dave@musical-dot-demon-dot-co.uk> ha scritto nel messaggio
news:untsc43CIHA.5976@TK2MSFTNGP02.phx.gbl...
CMyCollection : public std::vector<CMyThing>;
[...]
Could you please try to use a Has-A "embedding" relationship (not Is-A via
inheritance), i.e. : putting a private/protected instance of
std::vector<CMyThing> into CMyCollection.
CMyCollection::FillIn()
{
CMyThing thing;
for( allthings )
{
thing = .... // fill in the thing
push_back( thing ); //*********
}
}
[...]
I am being told that the memory leak is associated with the CMyThing's
copy constructor invoked by push_back() above.
How can that be?
It would be interesting to see some code for CMyThing... (maybe it has got
some non-smart pointers that are not correctly copied, or it hasn't got a
virtual destructor that would be required...).
Also, you should pay attention about the C/C++ run-time used by each module
(DLLs and EXE).
I think it should be the same (e.g. debug multithreaded DLL, or
multithreaded DLL for release builds).
Even stranger, I have had all of this present in the code for years and a
memory leak has only been reported recently.
Maybe you are now using VS2005 which implements better checking for memory
leaks than VC6 or 2003...
Ciao
Giovanni