Segmentation fault when evaluating 3^3^3^3
I evaluated "3^3^3^3" in the notebook and got a segmentation fault. Could somebody check if they can replicate this and file a bug report if appropriate?
Traceback (most recent call last): File "<stdin>", line 1, in <module> File "_sage_input_11.py", line 10, in <module> exec compile(u'open("___code___.py","w").write("# -- coding: utf-8 --\n" + _support_.preparse_worksheet_cell(base64.b64decode("M14zXjNeMw=="),globals())+"\n"); execfile(os.path.abspath("___code___.py")) File "", line 1, in <module>
File "/tmp/tmpsWGDUr/___code___.py", line 3, in <module> exec compile(u'_sage_const_3 *_sage_const_3 *_sage_const_3 **_sage_const_3 File "", line 1, in <module>
File "integer.pyx", line 1897, in sage.rings.integer.Integer.__pow__ (sage/rings/integer.c:12823) RuntimeError: Segmentation fault
EDIT: 4.7.2, compiled from source on Debian 6.0.3 64bit.
Happens in the command line as well.
2^2^2^2 is fine. 4^4^4^4 gives "RuntimeError: exponent must be at most 9223372036854775807", which is not properly documented (not in "Integer?").
Something completely unrelated: when one asks a question anonymously, one would expect their comments on that question to be anonymous too.
2^(2^31) is a segfault. 2^(2^31-1) cannot allocate enough memory, so I assume it works.
3^(2^31-1) is a segfault. 3^(2^30-1) isn't. Anyway, I can't imagine this being very helpful to anybody, sorry for spamming comments. I won't actively try to watch this question, so don't expect replies from me, and certainly don't suggest that I file a bug report myself.