[shell-coding] Re: Bad Pointer errors all over the place
From: "Brandon Sneed" <bsneed@xxxxxxxxx>
To: <shell-coding@xxxxxxxxxxxxx>
Date: Thu, 24 Oct 2002 09:09:24 -0500
You probably want to make sure that you have it set to check for handle
leaks. I don't remember if its on by default, but i've found it to be quite
good at finding that stuff. Be sure you're running in debug mode,
instrumented, etc. Let me know if you have any other q's.
niv
----- Original Message -----
From: "Daij-Djan" <Daij-Djan@xxxxxxxxxxxxxxx>
To: <shell-coding@xxxxxxxxxxxxx>
Sent: Thursday, October 24, 2002 7:23 AM
Subject: [shell-coding] Bad Pointer errors all over the place
> Geoshell 6 is 'leaking' memory and GDI resources. To find out why/how
> and when, I got a trial of Boundschecker 7. Unfortunately, the results
> have only further confused me.
> No memory is leaked and no GDI resources are lost!?
> The only errors Boundschecker finds concern freeing strings.
> We use CComBSTR and CComVariant and whenever a BSTR is freed
> Boundschecker reports a:
>
> Bad Pointer: 0x3A6AE8C passed to SysFreeString. In CComBSTR::Empty() or
> in CComVariant::Clear()
>
> The error occurs x thousand times, depending on how long you run the
> program. It happens in any function and at any time.
> The BSTR is a valid 0 terminated string... I don't have any idea of what
> the stupid program thinks we're doing wrong. :)
>
>
>
> __________________________________________________
> Subscription options and archive:
> http://www.freelists.org/list/shell-coding
__________________________________________________
Subscription options and archive:
http://www.freelists.org/list/shell-coding
