Re: Memory leak

[Fernando L. <fer...@gm...>]

Excellent !

I've updated my trunk copy to r232 and now the test with simple.cxx works
fine without any leak.
(I changed the PYCXX_ADD_..._METHOD sentences to the new syntax).

The changes in ExtensionType.hxx are very subtle, and I can imagine the
difficulty to find them.

Again, thank you for the fast response.

Fernando


2010/4/10 Barry Scott <ba...@ba...>

>
> On 9 Apr 2010, at 22:07, Barry Scott wrote:
>
> I have reproduced the mem leak on the mac and fedora.
>
> I'm looking into the problem.
>
> Barry
>
>
> This was hard to debug using any build of python with
> its own memory allocator enabled. This prevents malloc
> debug tools from finding the  real location of the leak.
>
> I build python with --without-pymalloc which tells python
> to use malloc and free.
>
> valgrind then found the memory leak and a coding error.
>
> This is fixed in r232. Please test in your setup and confirm
> the memory leak is fixed.
>
> Barry
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> CXX-Users mailing list
> CXX...@li...
> https://lists.sourceforge.net/lists/listinfo/cxx-users
>
>


-- 
Fernando Libonati
fernando.libonati at gmail.com