Re: User exception

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Dave (dave5397_at_btinternet.com)
Date: 05/07/04 

Date: Fri, 7 May 2004 10:40:50 +0100

No, it's a simple (non COM) dll and as previously suggested, I am not using
BSTR's at all, only LPSTR variables and I do no calls to SysFreeString.

How is an LPSTR variable actually passed as it's held as Unicode, so VB, I
assume must actually make an ANSI copy pointed to by LPSTR.

Thanks for looking at this - any other ideas?

"Kim Gräsman" <kim@mvps.org> wrote in message
news:OgxF#DANEHA.1392@TK2MSFTNGP09.phx.gbl...
> Dave,
>
> > > "User breakpoint called from code at ..."
> >
> > That's an assert. May happen because the memory is corrupted.
>
> More specifically, IIRC, this is from one of the OS allocators. I /think/
> I've seen this before when someone calls SysFreeString multiple times on
the
> same pointer, i.e. frees an already freed BSTR.
>
> My immediate guess is you have a property or method returning a BSTR, and
> that you're not copying it for [out]. If you have one of those, can you
post
> [parts of] the code?
>
> Kim
>
>