Re: Weird 0x80010105 error

From: languy (jni_at_online.stofanet.dk)
Date: 07/28/04 

Date: Wed, 28 Jul 2004 14:46:05 +0200

Thanks for the advice about the Detach() method on bstr_t strings, I will
remember this in the future. Now I think it is time to start a code review
to eliminate the memory bug(s). I assume the heap corruption be the direct
cause to some invalid com pointers, right?

Thanks in regards,
Jess

"Brian Muth" <bmuth@mvps.org> wrote in message
news:e64c8m$cEHA.2236@TK2MSFTNGP10.phx.gbl...
> Looks like a heap corruption to me. I would suggest a code review to watch
> all your string allocations and deallocations, and whatever else is
> allocated from the heap. It really isn't possible to comment more
> specifically based on what you have shown so far...
>
> BTW, as an aside I note that you repeatedly use *ec =
_bstr_t("xxx").copy();
> when the construct *ec = _bstr_t("xxx").Detach() is much more efficient
> (just so you are aware....)
>
> Best regards,
>
> Brian
>
>

Relevant Pages