Re: Tracing CComBSTR leaks

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@xxxxxxxx
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

"Richard Hollis" <richnews@xxxxxxxxxxxxxxxxx> wrote in message
news:1168902219.045065.59430@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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



.

Relevant Pages
Loading