Re: [evolution-patches] leaky camel



Umm, whats the test case for this ...

That code allocates its own messageinfo, and then fills it out.  It
can't have been set before!

If you're gettng that leaked, then something else is overwriting it or
not freeing it.

And btw, even if you needed to, you can just do free(mi->references), as
the sizeof operator doesn't ever derefernce, since its a compile-time
pseudofunction.

On Fri, 2003-06-20 at 02:31, Larry Ewing wrote:
> The old code happily overwrites the previous array.
> 
> --Larry




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]