Closed GoogleCodeExporter closed 9 years ago
The output I get from the sample code is a trace dump with:
RuntimeError: maximum recursion depth exceeded in cmp
which seems exactly right to me -- i.e., I don't see a segfault (with my mac's
system-installed Python)
because it does use a very large stack and so can actually support ridiculously
high recursion-limit (and this
code exceeds even that). Segmentation faults are typical of runaway recursion
when you've set the limit
higher than your version of Python can actually support, e.g.:
import sys
sys.setrecursionlimit(1500000)
def r(): return r()
r()
DOES give a segmentation fault.
Unless you can reproduce the problem with a non-recursion case, I'll have to
close this as unrelated to gmpy.
Original comment by alea...@gmail.com
on 28 Oct 2008 at 2:19
gmpy 1.04 fixed a memory allocation bug that did limit the size of the string
representation. However, your example would still exceed the memory limits of
most
computers. There is nothing else that can be done from the gmpy side.
Original comment by casevh
on 8 Apr 2009 at 5:19
Original issue reported on code.google.com by
Samphip...@googlemail.com
on 28 Oct 2008 at 1:46