Ask Your Question

Revision history [back]

prime_factors(2^100000000000000) output

After trying prime_factors(2^100000000000000) I received all this

[...bunch of paths in my pc...]

Attaching gdb to process id 5477. GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see:

Stack backtrace

Cython backtrace

Exception: <class 'gdb.error'=""> No registers.

Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operation not permitted. No stack. Traceback (most recent call last): File "<string>", line 118, in <module> File "<string>", line 90, in invoke File "<string>", line 94, in newest_first_order error: No registers. warning: Inferior ID 1 has no threads.

Saved trace to /home/esteban/.sage/crash_logs/sage_crash_zXpf5F.log

Unhandled SIGSEGV: A segmentation fault occurred in Sage. This probably occurred because a compiled component of Sage has a bug in it and is not properly wrapped with sig_on(), sig_off(). You might want to run Sage under gdb with 'sage -gdb' to debug this.

Sage will now terminate.

What is that? Should I do something? Did it (unsuccesfully) try to autoreport bug?