Em 9 de novembro de 2011 23:27, Paulo César Pereira de Andrade
<paulo.cesar.pereira.de.andr...@gmail.com> escreveu:
> Em 9 de novembro de 2011 23:24, Paulo César Pereira de Andrade
> <paulo.cesar.pereira.de.andr...@gmail.com> escreveu:
>
>> But, since gmpy call to mp_set_memory_functions is kind of redundant,
>> as it just ends up calling malloc/realloc/free anyway, with this patch:
>
> Err, this patch probably should require an environment variable, because
> what it calls actually is:
> if(!(res = PyMem_Malloc(usize)))
> Py_FatalError("mp_allocate failure");
> ...
> if(!(res = PyMem_Realloc(ptr, unew)))
> Py_FatalError("mp_reallocate failure");
> ...
> PyMem_Free(ptr);
>
> I think this may be related to some double free issues I noticed some
> time ago.
I opened two upstream tickets about it:
http://code.google.com/p/gmpy/issues/detail?id=49
http://code.google.com/p/mpmath/issues/detail?id=215
In the meantime, I will take the safe path of making the sagemath
package conflict with gmpy.
Paulo
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
