[shell-coding] Re: Bad Pointer errors all over the place

  • From: "Donelle Sanders" <donelle_sanders@xxxxxxxxxxx>
  • To: shell-coding@xxxxxxxxxxxxx
  • Date: Thu, 24 Oct 2002 15:14:35 +0000

In the PSDK there is a macro that prints to the debugger addref/release of all objects in the running program, the macro starts of with _ATL_INTERFACE or something like that. You have to define it in the stdafx.h this is for ATL only though.

 

-Matrice64

>From: "Daij-Djan"
>Reply-To: shell-coding@xxxxxxxxxxxxx
>To:
>Subject: [shell-coding] Re: Bad Pointer errors all over the place
>Date: Thu, 24 Oct 2002 16:38:41 +0200
>
>Jaykul said that maybe we don't leak memory but instead just don't
>release all com objects.
>Can we somehow build a list of all unreleased com objects?
>
>-----Original Message-----
>From: shell-coding-bounce@xxxxxxxxxxxxx
>[mailto:shell-coding-bounce@xxxxxxxxxxxxx] On Behalf Of Brandon Sneed
>Sent: Donnerstag, 24. Oktober 2002 16:09
>To: shell-coding@xxxxxxxxxxxxx
>Subject: [shell-coding] Re: Bad Pointer errors all over the place
>
>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"
>To:
>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:
> > //www.freelists.org/list/shell-coding
>
>
>__________________________________________________
>Subscription options and archive:
>//www.freelists.org/list/shell-coding
>
>
>__________________________________________________
>Subscription options and archive:
>//www.freelists.org/list/shell-coding

Internet access plans that fit your lifestyle -- join MSN. Click Here __________________________________________________ Subscription options and archive: //www.freelists.org/list/shell-coding

Other related posts:

  1. Home
  2. shell-coding
  3. Archive
  4. 10-2002