ASKSAGE: Sage Q&A Forum - RSS feedhttps://ask.sagemath.org/questions/Q&A Forum for SageenCopyright Sage, 2010. Some rights reserved under creative commons license.Mon, 12 Dec 2022 07:45:40 +0100Are rings of integers incompatible with multiprocessing?https://ask.sagemath.org/question/65322/are-rings-of-integers-incompatible-with-multiprocessing/ The code below crashen on sage 9.5:
from multiprocessing import Pool
def print_stuff(stuff):
print(stuff)
pool = Pool(processes = 1 ) #make a pool objects
K.<z> = CyclotomicField(16)
OK = K.ring_of_integers()
task = pool.apply_async( print_stuff, (OK, ) ) #load the tasks into the list
outputs = task.get() #complete the tasks
print(outputs) #print the outputs
Am I handling rings of integers wrong? How can I access them in parallel without recomputing?
The message ends with:
File "sage/matrix/matrix_integer_dense.pyx", line 2066, in sage.matrix.matrix_integer_dense.Matrix_integer_dense.echelon_form (build/cythonized/sage/matrix/matrix_integer_dense.cpp:18127)
File "sage/matrix/matrix_integer_dense.pyx", line 5744, in sage.matrix.matrix_integer_dense.Matrix_integer_dense._hnf_pari (build/cythonized/sage/matrix/matrix_integer_dense.cpp:47633)
cysignals.signals.SignalError: Segmentation faultAlex KareninMon, 12 Dec 2022 07:45:40 +0100https://ask.sagemath.org/question/65322/EllipticCurve.rank (mwrank) leads to segmentation fault in Sage 9.5/9.0, but to a regular exception in Sage 8.2. Is this a bug of Sage 9.5/9.0?https://ask.sagemath.org/question/61296/ellipticcurverank-mwrank-leads-to-segmentation-fault-in-sage-9590-but-to-a-regular-exception-in-sage-82-is-this-a-bug-of-sage-9590/Hello,
when I try to calculate the rank of elliptic curves, Sage 8.2 works well and tells me in some cases by throwing exceptions, that it could not calculate it. See code example below.
In Sage 9.5 (as well as in Sage 9.0) the same code leads to a segmentation fault. To be more precise, the 1st try of EllipticCurve.rank() leads to a "divison by zero" exception, And the 2nd try (for the same curve or for a curve that leads to the same problem) then leads to segmentation fault.
You may reproduce it on SageMathCell (sagecell.sagemath.org). Simply copy the code below and evaluate.
If you agree that this is a bug - what should I do to open a ticket?
Best Regards
Daniel Lauer
--
<pre><code>
print("Version of Sage: {}".format(version()))
print("\n(1) Everything okay in this simple case of calling EllipticCurve.rank():")
E = EllipticCurve([0,4321,0,1234,0])
print("E = {}".format(E))
k = E.rank(only_use_mwrank=True)
print("rank = {}\n".format(k))
print("\n(2) Still okay: Same method for different curve will lead to an exception. That's okay.")
print(" Problem B (prio 2) is: The exception is a different one, now.")
print(" In Sage 8.2, it was 'rank not provably correct (lower bound: 0)' -- and I think, this is the correct one.")
print(" In Sage 9.0 and 9.5 the exception is 'division by zero'")
E = EllipticCurve([0,20752947797,0,74237199888641440000,0])
print("E = {}".format(E))
try:
k = E.rank(only_use_mwrank=True)
print("rank = {}\n".format(k))
except Exception as exc:
print("Exception: {}".format(str(exc)))
print("\n(3) So, let's do a rank computation for a different curve. This works well in all versions of Sage.")
E = EllipticCurve([0,5432,0,2345,0])
print("E = {}".format(E))
k = E.rank(only_use_mwrank=True)
print("rank = {}\n".format(k))
print("\n(4) Now problem A (prio 1) will occur: If we start a rank computation that shows the same problem as in (2), ...")
print(" ... in Sage 8.2, everything is fine: the same exception will be returned, again.")
print(" ... in Sage 9.0 and 9.5, Sage crashes with 'segmentation fault'")
E = EllipticCurve([0,20752947797,0,74237199888641440000,0])
#E = EllipticCurve([0,108066172377/1024,0,6926399795059430625/4096,0]) # the same behaviour if we choose this elliptic curve here instead of the former one
print("E = {}".format(E))
try:
k = E.rank(only_use_mwrank=True)
print("rank = {}\n".format(k))
except Exception as exc:
print("Exception: {}".format(str(exc)))
print("\n(5) Further code: ...")
print(" ... in Sage 8.2, everything is fine: the code is executed.")
print(" ... in Sage 9.0 and 9.5 this code is never reached because of segmentation fault.")
</code></pre>
Daniel LauerSat, 26 Feb 2022 18:13:10 +0100https://ask.sagemath.org/question/61296/segmentation fault when find gcd of fraction and sqrthttps://ask.sagemath.org/question/60032/segmentation-fault-when-find-gcd-of-fraction-and-sqrt/ sage: (3/2).gcd(sqrt(2))
------------------------------------------------------------------------
(no backtrace available)
------------------------------------------------------------------------
Unhandled SIGSEGV: A segmentation fault occurred.
This probably occurred because a *compiled* module has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Python will now terminate.
------------------------------------------------------------------------
[1] 90215 segmentation fault sage
sage crashed when I want to get gcd of a fraction and an sqrtvnbThu, 02 Dec 2021 05:11:55 +0100https://ask.sagemath.org/question/60032/Plotting with sagemath 9.3 on windows 10 causes segmentation faulthttps://ask.sagemath.org/question/59710/plotting-with-sagemath-93-on-windows-10-causes-segmentation-fault/ I installed SageMath 9.3 on a new Dell laptop running windows 10.
Running Sagemath 9.3 in the shell produces a segmentation fault. (see screenshot)
Runnins Sagemath 9.3 in a Jupyter notebook kills the kernel (see screenshot)
Running Python 3.8 (Anaconda) in Jupyter notebook produces expected result.
Running Julia 1.6.3 (launching jupyter from Anaconda Navigator) works (see screenshot
I'm sorry, I have screen shots of these runs, but an unable to upload because I haven't enough points.profceliaFri, 12 Nov 2021 14:28:45 +0100https://ask.sagemath.org/question/59710/Segmentation fault calling is_irreducible()https://ask.sagemath.org/question/56676/segmentation-fault-calling-is_irreducible/ sage: R.<X> = PolynomialRing(GF(17^2))
sage: (X^2).is_irreducible()
---------------------------------------------------------------------------
SignalError Traceback (most recent call last)
<ipython-input-143-f9ef3e37d5e5> in <module>
----> 1 (X**Integer(2)).is_irreducible()
/usr/lib/python3/dist-packages/sage/rings/polynomial/polynomial_zz_pex.pyx in sage.rings.polynomial.polynomial_zz_pex.Polynomial_ZZ_pEX.is_irreducible (build/cythonized/sage/rings/polynomial/polynomial_zz_pex.cpp:16857)()
350 self._parent._modulus.restore()
351 if algorithm=="fast_when_false":
--> 352 sig_on()
353 res = ZZ_pEX_IterIrredTest(self.x)
354 sig_off()
SignalError: Segmentation fault
sage: version()
'SageMath version 9.2, Release Date: 2020-10-24'
dairaFri, 16 Apr 2021 20:10:00 +0200https://ask.sagemath.org/question/56676/Unknown installation problem in Windows 7https://ask.sagemath.org/question/54245/unknown-installation-problem-in-windows-7/ I installed Sagemath 9.1 from the executable. Almost nothing works: when I execute from desktop icon it just crashes, if I do from icon that says Notebook it crashes after saying
"Use Control-C to stop ...."
If I execute the shell, I can use without problem "sage -python", "sage -gap", etc, but if I execute
sage -c
then it says
------------------------------------------------------------------------
Unhandled SIGSEGV: A segmentation fault occurred.
This probably occurred because a *compiled* module has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Python will now terminate.
------------------------------------------------------------------------
/opt/sagemath-9.1/src/bin/sage-python line 2: 1615 Segmentation fault (overflow memory)sage -python "$@"
Do you have any suggestions about how to solve the problem? I reinstalled Sagemath several times, but everytime there is the same problem. X1729Sun, 15 Nov 2020 14:35:41 +0100https://ask.sagemath.org/question/54245/Crash with polynomial over "Givaro" finite fieldhttps://ask.sagemath.org/question/53696/crash-with-polynomial-over-givaro-finite-field/I would like to solve a system of equations
in a finite field of prime order $p$
(illustrated below with $p = 229$).
The system consists in four equations and has four unknowns
$a_0$, $a_1$, $a_2$, $a_3$.
It depends on parameters $\alpha_i$, $b_i$, all in $F(p)$,
for $i = 1, 2, 3, 4$.
The four equations are
$$a_0 + a_1 \alpha_1 + a_2 \alpha_1^2 + a_3 \alpha_1^3 = b_1$$
$$a_0 + a_1 \alpha_2 + a_2 \alpha_2^2 + a_3 \alpha_2^3 = b_2$$
$$a_0 + a_1 \alpha_3 + a_2 \alpha_3^2 + a_3 \alpha_3^3 = b_3$$
$$a_0 + a_1 \alpha_4 + a_2 \alpha_4^2 + a_3 \alpha_4^3 = b_4$$
To do this I have tried with the following examples:
pm = 229
bp = 229
F.<x> = GF(pm, impl='givaro')
R.<a0, a1, a2, a3> = PolynomialRing(F)
def NP(a):
return F(ZZ(a).digits(bp)) # integer to polynomial
eqns = [a0 + a1*NP(2) + a2*NP(2)^2 + a3*NP(2)^3 - NP(78),
a0 + a1*NP(3) + a2*NP(3)^2 + a3*NP(3)^3 - NP(136),
a0 + a1*NP(4) + a2*NP(4)^2 + a3*NP(4)^3 - NP(179),
a0 + a1*NP(5) + a2*NP(5)^2 + a3*NP(5)^3 - NP(166)]
A = matrix(F, [[eqn.coefficient(b) for b in R.gens()] for eqn in eqns])
b = vector(F, [-eqn.constant_coefficient() for eqn in eqns])
X = A.solve_right(b)
print(X)
But it shows erros:
Unhandled SIGSEGV: A segmentation fault occurred.
This probably occurred because a *compiled* module has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Python will now terminate.
------------------------------------------------------------------------
/usr/share/sagemath/bin/sage-python: line 2: 7655 Segmentation fault (core dumped) sage -python "$@"
How can I fix this?MKSFri, 02 Oct 2020 01:48:21 +0200https://ask.sagemath.org/question/53696/Segmentation fault in magma interfacehttps://ask.sagemath.org/question/53622/segmentation-fault-in-magma-interface/ I'm trying to use the Magma computational algebra interface to do polynomial interpolation for large lists of size 2^18. My code has the following:
p = magma("Interpolation(%s,%s)" % (I,V)).sage()
where I and V are lists each with 2^18 elements. This works just fine for smaller lists but for this size it looks like magma gets a segfault with the following error:
> File "/SageMath/local/lib/python3.7/site-packages/sage/interfaces/magma.py", line 631, in set
raise TypeError("Error executing Magma code:\n%s" % out)
> TypeError: Error executing Magma code:
> Magma: Internal error
> Machine type: intel64-linux
> Memory usage: 49264.41MB
> Segmentation fault
I know that Magma by itself can do the computation, but I would like to get it working using the Sage interface. Is this just not possible or am I doing something wrong? dennySun, 27 Sep 2020 17:49:22 +0200https://ask.sagemath.org/question/53622/sage test image.py causes sagmentation faulthttps://ask.sagemath.org/question/43185/sage-test-imagepy-causes-sagmentation-fault/I build sage 8.2 from source. using gcc 7.3.0 compiler. [I'm using ubuntu 18.04 LTS]
When I test my sage I got "sage -t --warn-long 25.2 src/sage/repl/image.py # Killed due to segmentation fault" message.
How can I solve it?
Thank you.
ps. when I test image.py manually this error only occurs when I test below example.
EXAMPLES::
sage: from sage.repl.image import Image
sage: img = Image('1', (16, 16), 'white')
sage: from sage.repl.rich_output import get_display_manager
sage: dm = get_display_manager()
sage: img._rich_repr_(dm)
OutputImagePng container
sage: img = Image('F', (16, 16), 'white') # not supported in PNG
sage: img._rich_repr_(dm) #This causes sagementation fault
OutputImageGif container
jun1234Sat, 28 Jul 2018 10:04:25 +0200https://ask.sagemath.org/question/43185/could someone please try this integral? segmentation fault generatedhttps://ask.sagemath.org/question/42717/could-someone-please-try-this-integral-segmentation-fault-generated/Could someone please try this integral on their PC? I am getting sage core dump from it.
Wanted to see if it just my sage or if it happens to others. Make sure to save your sage work before trying this.
>sage
┌────────────────────────────────────────────────────────────────────┐
│ SageMath version 8.3.beta6, Release Date: 2018-06-17 │
│ Type "notebook()" for the browser-based notebook interface. │
│ Type "help()" for help. │
└────────────────────────────────────────────────────────────────────┘
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Warning: this is a prerelease version, and it may be unstable. ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
sage: var('x m a b')
(x, m, a, b)
sage: integrate(x^m/sqrt(a + b*x^(2 - m)),x)
;;;
;;; Detected access to protected memory, also kwown as 'bus or segmentation fault'.
;;; Jumping to the outermost toplevel prompt
;;;
When I use other algorithm, no core dump
sage: integrate(x^m/sqrt(a + b*x^(2 - m)),x,algorithm="giac")
integrate(x^m/sqrt(b*x^(-m + 2) + a), x)
I am on Linux Manjaro 17.1. Intel PC. Installed sage, compiled from sources, using Manjaro package manager pacman.
And just in case, I also posted bug report here https://trac.sagemath.org/ticket/25636
Thank you
--NasserNasserFri, 22 Jun 2018 22:25:30 +0200https://ask.sagemath.org/question/42717/Segmentation fault (core dumped) SageMath version 8.2https://ask.sagemath.org/question/42664/segmentation-fault-core-dumped-sagemath-version-82/Sage still core dumps. I thought earlier it was fixed, but it is not.
/usr/bin/sage-python: line 2: 2794 Segmentation fault (core dumped) sage -python "$@"
**Short summary of the problem**: When I run a sage script which iterates over large list of integrals, then call maxima, it segfault, but only when the list is long. (trial and error shows when it is over 45 entries)
When I change the algorithm from "maxima" to "fricas", the script runs and it works. NO OTHER CHNAGES.
When the list is short, using maxima no longer causes a segfault. So it seems like a memory corruption for me.
Why when the list is short it works, but when adding one more entry to the list, it segfault? And only when using maxima?
The script uses Python multiprocessing.
The script is long, but only because the list is long. So I was not sure if I should post it here. (I could if needed) but I put a link to it here. Please see https://www.12000.org/tmp/sage_segfault/test_maxima.sage
To run, simply download to any folder and type `./test_maxima.sage`
It will segfault. I tried it on **sage 8.2**, **sage 8.1**, **sage 8.3 beta 6**. On latest **Manjora linux 17.1** and also on **Linux mint 19** and tried it on standalone PC running Linux and inside Virtual box running Linux.
Could someone please try this script to see if they get the segfault? Otherwise, I could not test maxima for integration and will have just leave it out. I do not know where the dump file is written to. Does any one know? I do not see it in same folder I am running the script from.NasserTue, 19 Jun 2018 15:20:18 +0200https://ask.sagemath.org/question/42664/can not install -> segmentation faulthttps://ask.sagemath.org/question/41276/can-not-install-segmentation-fault/ I am running MacOSX 10.6.8
Here is what I get
"/Applications/SageMath-7.1.app/Contents/Resources/sage/src/bin/sage-env: line 407: 2160 Segmentation fault "$SAGE_ROOT/local/bin/python" -c 'import pkg_resources; pkg_resources.get_distribution("matplotlib").version' 2> /dev/null"
AND this
"/Applications/SageMath-7.1.app/Contents/Resources/sage/src/bin/sage: line 387: 2172 Segmentation fault sage-location
logout"
newsageuser0226Tue, 27 Feb 2018 05:35:23 +0100https://ask.sagemath.org/question/41276/Getting code dumped error in sage code for weil-pairing ?https://ask.sagemath.org/question/35770/getting-code-dumped-error-in-sage-code-for-weil-pairing/ I have been trying to run a sage code for doing weil-pairing which gives the following error message:
' */usr/lib/sagemath/local/bin/sage-python: line 2: 15172 **Segmentation fault (core dumped)** sage -python "$@"* '
I tried sage versions 7.2, 7.3, and 7.4 but still getting same error. I am using Ubuntu 14.04. But it works in another system running Ubuntu. Someone please help.
# Weil Pairing Example
# Example 5.43 in IMC
# E: y^2 = x^3 + 30x + 34 mod 631
p = 631
a = 30
b = 34
E = EllipticCurve(GF(p), [a, b])
print E
P = E((36, 60))
Q = E((121, 387))
n = 5
S = E((0, 36))
print "P =", P.xy()
print "Q =", Q.xy()
print "#P = #Q =", n
var('x y')
def g(P, Q):
(x_P, y_P) = P.xy()
(x_Q, y_Q) = Q.xy()
if x_P == x_Q and y_P + y_Q == 0:
return x - x_P
if P == Q:
slope = (3 * x_P^2 + a)/(2 * y_P)
else:
slope = (y_P - y_Q)/(x_P - x_Q)
return (y - y_P - slope * (x - x_P))/(x + x_P + x_Q - slope^2)
def miller(m, P):
m = bin(m)[3:]
n = len(m)
T = P
f = 1
for i in range(n):
f = f^2 * g(T, T)
T = T + T
if int(m[i]) == 1:
f = f * g(T, P)
T = T + P
return f
def eval_miller(P, Q):
f = miller(n, P)
(x1, y1) = Q.xy()
return f(x = x1, y = y1)
def weil_pairing(P, Q, S):
num = eval_miller(P, Q+S)/eval_miller(P, S)
den = eval_miller(Q, P-S)/eval_miller(Q, -S)
return (num/den)
e = weil_pairing(P, Q, S)
print "e(P, Q) =", e
# e^n = 1
print "e(P, Q)^n =", e^n
P3 = P * 3
Q4 = Q * 4
e12 = weil_pairing(P3, Q4, S)
print "[3]P =", P3.xy()
print "[4]Q =", Q4.xy()
print "e([3]P, [4]Q) =", e12
print "e(P, Q)^12 =", e^12SP HarishTue, 29 Nov 2016 05:46:08 +0100https://ask.sagemath.org/question/35770/integral() failing with "segmentation fault"https://ask.sagemath.org/question/10966/integral-failing-with-segmentation-fault/Hi sage community
My question again arises from exercises in technical chemistry done in sage. I wanted to calculate an definite integral (number of transfer units).
var('x')
ys=0.06+2*(x-0.0275)
xs=ys/1.516
#my function
i=1/(xs/(1+xs)-x/(1+x))
#print i
#show(plot(i,x,0,0.03))
#I, the indefinite integral of i
I=integral(i,x)
#print I
#show(plot(I,x,0,0.03))
#three methods too calculate the integral
print n(I(x=0.0275)-I(x=0))
print numerical_integral(i,0,0.0275)
print integral(i,x,0,0.275)
The first two methods work fine. The last method gives me the infinite of the following messages.
;;;
;;; Detected access to protected memory, also kwown as 'bus or segmentation fault'.
;;; Jumping to the outermost toplevel prompt
;;;
This is a bug, isn't it? However, i have no idea how integrate() works.
Greetings, marvmarvMon, 27 Jan 2014 10:37:16 +0100https://ask.sagemath.org/question/10966/save command in SAGEhttps://ask.sagemath.org/question/10496/save-command-in-sage/I'm trying to save a 'big' rational matrix in SAGE, but I'm running into problems.
After computing my matrix A, which has size 5 x 10,000 and each entry contains rational numbers in fraction form with total number of digits for numerator and denominator more than 10 pages, I run the following command:
save(A, DATA + 'A').
This gives me the following error message:
Traceback(most recent call last):
...
RuntimeError: Segmentation fault.
After this, I can't access A at all any more. In other words, when I try to compute say A[2,3], I get an error. However, before running the save command I was able to compute this entry. Also, I tried the same save command with a 'smaller' matrix and that worked fine. I should also note that I'm using a laptop with 64-bit operating system, x64-based processor, Windows 8, i7 CPU @ 2.40 GHz and 8 GB RAM. Let me know if you need further information. My questions are:
1. Why can't I save my matrix? Why do I get the above error message? What does it mean?
2. How can I save my matrix A? Is there any other way I can save it?Sandi XhumariSun, 01 Sep 2013 18:07:15 +0200https://ask.sagemath.org/question/10496/sage crashes while interpolatinghttps://ask.sagemath.org/question/9146/sage-crashes-while-interpolating/ f_interpolation = scipy.interpolate.interp2d(*zip(*matrix(A)),kind='cubic')
plot_interpolation = contour_plot(lambda x,y:
f_interpolation(x,y)[0], (22.423,22.439),(37.07,37.08) ,cmap='jet', contours=numpy.arange(0,1400,100), colorbar=True)
plot_all = plot_interpolation
plot_all.show(,axes_labels=["m", "m"])
I am running this command to interpolate the data contained in matrix(A).
matrix(A) is 1800 x 3 dense matrix over Real Double Field. Sage crashes everytime i do this both in a quad core Amd with 8GB of ram(kubuntu 12.04 64bit, in both the binary and compiled from source versions) and a netbook Lenovo s9e with Intel Atom and 1GB of ram(kubuntu 12.04 32bit, binary version of sage).It returns this message:
/home/user/Sage/sage-5.0.1/local/lib/libcsage.so(print_backtrace+0\
x31)[0x7fc18b464ea9]
/home/user/Sage/sage-5.0.1/local/lib/libcsage.so(sigdie+0x14)[0x7f\
c18b464edb]
/home/user/Sage/sage-5.0.1/local/lib/libcsage.so(sage_signal_handl\
er+0x20c)[0x7fc18b464b06]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7fc18f3f4cb0]
/home/user/Sage/sage-5.0.1/local/lib/python2.7/site-packages/scipy\
/interpolate/_fitpack.so(fprank_+0xdb0)[0x7fc15d29f4e0]
/home/user/Sage/sage-5.0.1/local/lib/python2.7/site-packages/scipy\
/interpolate/_fitpack.so(fpsurf_+0x67b8)[0x7fc15d2990d8]
/home/user/Sage/sage-5.0.1/local/lib/python2.7/site-packages/scipy\
/interpolate/_fitpack.so(surfit_+0xa08)[0x7fc15d289c18]
/home/user/Sage/sage-5.0.1/local/lib/python2.7/site-packages/scipy\
/interpolate/_fitpack.so(+0x4c7b)[0x7fc15d26cc7b]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alFrameEx+0x53a5)[0x7fc18f6f0e45]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCodeEx+0x855)[0x7fc18f6f2a95]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alFrameEx+0x5420)[0x7fc18f6f0ec0]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCodeEx+0x855)[0x7fc18f6f2a95]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(+0x73843)\
[0x7fc18f675843]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyObject_\
Call+0x53)[0x7fc18f64d7a3]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(+0x58f1f)\
[0x7fc18f65af1f]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyObject_\
Call+0x53)[0x7fc18f64d7a3]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(+0xac660)\
[0x7fc18f6ae660]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(+0xa8458)\
[0x7fc18f6aa458]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyObject_\
Call+0x53)[0x7fc18f64d7a3]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alFrameEx+0x2b2a)[0x7fc18f6ee5ca]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCodeEx+0x855)[0x7fc18f6f2a95]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(+0x7374c)\
[0x7fc18f67574c]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyObject_\
Call+0x53)[0x7fc18f64d7a3]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alFrameEx+0x2b2a)[0x7fc18f6ee5ca]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCodeEx+0x855)[0x7fc18f6f2a95]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alFrameEx+0x5420)[0x7fc18f6f0ec0]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alFrameEx+0x614b)[0x7fc18f6f1beb]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCodeEx+0x855)[0x7fc18f6f2a95]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCode+0x32)[0x7fc18f6f2bd2]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alFrameEx+0x515f)[0x7fc18f6f0bff]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCodeEx+0x855)[0x7fc18f6f2a95]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCode+0x32)[0x7fc18f6f2bd2]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyRun_Fil\
eExFlags+0xb0)[0x7fc18f715340]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(+0xe6cb8)\
[0x7fc18f6e8cb8]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alFrameEx+0x53a5)[0x7fc18f6f0e45]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCodeEx+0x855)[0x7fc18f6f2a95]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCode+0x32)[0x7fc18f6f2bd2]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alFrameEx+0x515f)[0x7fc18f6f0bff]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCodeEx+0x855)[0x7fc18f6f2a95]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCode+0x32)[0x7fc18f6f2bd2]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyRun_Fil\
eExFlags+0xb0)[0x7fc18f715340]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(+0xe6cb8)\
[0x7fc18f6e8cb8]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alFrameEx+0x53a5)[0x7fc18f6f0e45]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCodeEx+0x855)[0x7fc18f6f2a95]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyEval_Ev\
alCode+0x32)[0x7fc18f6f2bd2]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyRun_Int\
eractiveOneFlags+0x182)[0x7fc18f7162c2]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyRun_Int\
eractiveLoopFlags+0x4e)[0x7fc18f7164fe]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(PyRun_Any\
FileExFlags+0x4c)[0x7fc18f716aac]
/home/user/Sage/sage-5.0.1/local/lib/libpython2.7.so.1.0(Py_Main+0\
xbe5)[0x7fc18f729295]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7fc18f04976d]
/home/user/Sage/sage-5.0.1/local/bin/python[0x400661]
------------------------------------------------------------------------\
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.
------------------------------------------------------------------------\
If matrix(a) is smaller(like 600 x 3) i do get results and a graph, but even then, the interpolation stops soon and produces a graph which makes no sense. It warns about:
Warning: No more knots can be added because the number of B-spline
coefficients
already exceeds the number of data points m. Probably causes:
either
s or m too small. (fp>s)
kx,ky=3,3 nx,ny=11,15 m=72 fp=0.000114 s=0.000000
Any ideas?
**EDIT:**
Everytime there's this crash in the terminal i get the following message:
got EOF subprocess must have crashed...
**EDIT:**
It finally crashed again in sage 5.1CosmosWed, 11 Jul 2012 09:29:36 +0200https://ask.sagemath.org/question/9146/What is unhandled Sigsegvhttps://ask.sagemath.org/question/9101/what-is-unhandled-sigsegv/Hi,
I'm working with sage 4.7.2 on a virtual machine on windows 7. I have some more lines of code where I read some data tables and try to fit them with find_fit and than calculate confidence intervals. Suddenly I get and error of the following kind:
[...]
/home/sage/sage/local/lib/libpython2.6.so.1.0(PyRun_InteractiveLoopFlags\
+0x5b)[0xd1d8bb]
/home/sage/sage/local/lib/libpython2.6.so.1.0(PyRun_AnyFileExFlags+0x4e)\
[0xd1df3e]
/home/sage/sage/local/lib/libpython2.6.so.1.0(Py_Main+0xca0)[0xd2ce60]
/home/sage/sage/local/bin/python(main+0x27)[0x80485c7]
/lib/libc.so.6(__libc_start_main+0xe6)[0x126e36]
/home/sage/sage/local/bin/python[0x8048501]
------------------------------------------------------------------------
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.
------------------------------------------------------------------------
I found some a trac ticket concerning this but it does not help me. Also I do not know how to use the debugging command with the VM to give you further information or where to but the notebook and the data file so everyone could have a further look if wanted.
Do not hesitate to ask for additional information.
Again thanks in advancegod.oneThu, 21 Jun 2012 17:20:56 +0200https://ask.sagemath.org/question/9101/Segmentation fault when evaluating 3^3^3^3https://ask.sagemath.org/question/8605/segmentation-fault-when-evaluating-3333/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.chaesloc2Wed, 04 Jan 2012 10:35:08 +0100https://ask.sagemath.org/question/8605/