Re: Tracing CComBSTR leaks
Ah, I forgot to mention that then you should change the
implementation of all affected methods to free their
[in, out] arguments before assigning the return value...
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Alexander Nickolov" <agnickolov@mvps.org> wrote in message
news:O635SYZOHHA.1252@TK2MSFTNGP02.phx.gbl...
Any text editor that can search will do. Make sure you
have no [out] arguments throughout your IDL file. [in, out]
and [out, retval] are ok.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Richard Hollis" <richnews@littleredfrog.com> wrote in message
news:1168902219.045065.59430@q2g2000cwa.googlegroups.com...
I've come across some leaks in my ATL objects which are around the use
of CComBSTRs and [out] parameter - the documented behaviour unless
Empty is used. I think I've fixed most of them, but I want to be sure.
What tool(s) can I use to trap these leaks and ensure that I have
caught all of them? I'm debugging in the COM surrogate for IIS -
dllhost.
Thanks
Richard