I found the problem I think. Consider: time RR(0).exact_rational()
CPU times: user 0.81 s, sys: 0.39 s, total: 1.21 s Wall time: 1.23 0.81s for such a trivial command is not normal. Also memory consumption goes up a lot, presumably causing an out of memory error on systems with little memory. I suspect there is a bug in mpfr_get_z_exp(value1,value2) when value2 is zero. Michel On May 11, 10:49 am, Michel <[EMAIL PROTECTED]> wrote: > Very strange: I did the test again and this time it passed....! > I can't make it fail again. But it did fail on > two different machines on a clean sage 2.5 install. > > So I wonder what goes on. A buffer overflow? > > Michel > > On May 11, 10:11 am, Michel <[EMAIL PROTECTED]> wrote: > > > I posted this before but it did never appear. So I am trying again. > > > I get a doctest failure on two clean sage 2.5 installs on FC4 x86/32 > > in devel/sage-main/sage/rings/real_mpfr.pyx. > > Message: > > > "A mysterious error (perphaps a memory error?) occured, which may have > > crashed doctest." > > > A clean install on FC6 x86/32 does not exhibit this problem. > > > Any recommended procedure for debugging this? > > > Michel > > > PS. A quick perusal of install.log did not reveal anything special. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
