Re: heap corruption

On Mon, Mar 03, 2003 at 03:03:41AM -0500, Russell Yanofsky wrote:
> Branko Cibej wrote:
> > Russell Yanofsky wrote:
> >> This isn't generally true. The only situation where having two CRTs
> >> will lead to heap corruption is if a pointer malloc()ed in one DLL
> >> is free()d in another. Any DLL interface that is meant to be
> >> portable to different compilers (i.e. Visual C++, Borland,
> >> Metrowerks, Cygwin, Visual Basic) won't pass pointers back and forth
> >> this way. I'd be surprised if apr-iconv did this.
> >>
> > It does, actually.
>
> Oh. What about the other apache libaries and the berkeley library? Do they
> also require their callers to use malloc or free?
>
I believe bdb does.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~