Open numpy-gitbot opened 12 years ago
atmention:charris wrote on 2011-04-13
Hmm... This isn't SPARC so we can rule out the usual alignment problems. The call to cexp looks pretty routine and works here on x86_64. I can't tell right away if the call is to the numpy or the gcc version of cexp, but with the old compiler it may be the numpy version.
Can you find a simpler example that causes the same problem?
atmention:rgommers wrote on 2011-04-13
I'm guessing you're asking John, so CC'ing him.
trac user jdh2358 wrote on 2011-08-17
I can confirm that the seg fault still occurs on git HEAD numpy 2.0.0.dev-4386275
Here is a much simpler script that exposes it ::
import numpy as np
print np.__version__
xn = np.exp(2j)
And here is the stack trace: johnhatmention:udesktop253:~> sudo pstack /var/core/core.python.957 core '/var/core/core.python.957' of 28628: python test.py febf1928 cexp (0, 0, 0, 40000000, 1, 807dec0) + 1b0 fe8a6820 npy_cexp (8045420, 0, 0, 0, 40000000, 2) + 30 fe894fef nc_exp (8045460, 8212480, f, 8045460, 0, 0) + 3f fe877d7b PyUFunc_D_D (80454c4, 80454bc, 80454b4, fe894fb0, fe8a7aa9, 8045a9c) + 5b fe8892b2 trivial_two_operand_loop (0, 0, 0, 0, 0, 8212480) + 112 fe8a0eb5 PyUFunc_GenericFunction (81a3438, 807deac, 0, 8045a98, 80a31e0, 8045858) + 1465 fe8a13c0 ufunc_generic_call (81a3438, 807deac, 0, fe8cbfa0) + 70 feeb2d78 PyObject_Call (81a3438, 807deac, 0, 81a3018, 8061848, 0) + 28 fef11900 PyEval_EvalFrame (81a2ec4, 816c5e0, 8079824, 8079824) + 146c fef17708 PyEval_EvalCodeEx (816c5e0, 8079824, 8079824, 0, 0, 0) + 620 fef178af PyEval_EvalCode (816c5e0, 8079824, 8079824, 8061458, fef3d9ee, 0) + 2f fef3d095 PyRun_FileExFlags (feb91c98, 804627b, 101, 8079824, 8079824, 1) + 75 fef3d9ee PyRun_SimpleFileExFlags (feb91c98, 804627b, 1, 8045f88, fef454a1, 804627b) + 172 fef3e4fd PyRun_AnyFileExFlags (feb91c98, 804627b, 1, 8045f88) + 61 fef454a1 Py_Main (1, 804609c, feb1cf35, fea935a1, 29, feb96750) + 9d9 08050862 main (2, 804609c, 80460a8) + 22 08050758 _start (2, 8046274, 804627b, 0, 8046283, 80462ad) + 60
trac user jdh2358 wrote on 2011-08-17
Repost because my formatting was screwed.
I can confirm that the seg fault still occurs on git HEAD numpy 2.0.0.dev-4386275
Here is a much simpler script that exposes it
import numpy as np
print np.__version__
xn = np.exp(2j)
and here is the stack trace
johnhatmention:udesktop253:~> sudo pstack /var/core/core.python.957
core '/var/core/core.python.957' of 28628: python test.py
febf1928 cexp (0, 0, 0, 40000000, 1, 807dec0) + 1b0
fe8a6820 npy_cexp (8045420, 0, 0, 0, 40000000, 2) + 30
fe894fef nc_exp (8045460, 8212480, f, 8045460, 0, 0) + 3f
fe877d7b PyUFunc_D_D (80454c4, 80454bc, 80454b4, fe894fb0, fe8a7aa9, 8045a9c) + 5b
fe8892b2 trivial_two_operand_loop (0, 0, 0, 0, 0, 8212480) + 112
fe8a0eb5 PyUFunc_GenericFunction (81a3438, 807deac, 0, 8045a98, 80a31e0, 8045858) + 1465
fe8a13c0 ufunc_generic_call (81a3438, 807deac, 0, fe8cbfa0) + 70
feeb2d78 PyObject_Call (81a3438, 807deac, 0, 81a3018, 8061848, 0) + 28
fef11900 PyEval_EvalFrame (81a2ec4, 816c5e0, 8079824, 8079824) + 146c
fef17708 PyEval_EvalCodeEx (816c5e0, 8079824, 8079824, 0, 0, 0) + 620
fef178af PyEval_EvalCode (816c5e0, 8079824, 8079824, 8061458, fef3d9ee, 0) + 2f
fef3d095 PyRun_FileExFlags (feb91c98, 804627b, 101, 8079824, 8079824, 1) + 75
fef3d9ee PyRun_SimpleFileExFlags (feb91c98, 804627b, 1, 8045f88, fef454a1, 804627b) + 172
fef3e4fd PyRun_AnyFileExFlags (feb91c98, 804627b, 1, 8045f88) + 61
fef454a1 Py_Main (1, 804609c, feb1cf35, fea935a1, 29, feb96750) + 9d9
08050862 main (2, 804609c, 80460a8) + 22
08050758 _start (2, 8046274, 804627b, 0, 8046283, 80462ad) + 60
Original ticket http://projects.scipy.org/numpy/ticket/1713 on 2011-01-15 by atmention:rgommers, assigned to unknown.
Reported on the mailing list on 3 Jan 2011 by John Hunter.