[issue17706] Segfault in PyErr_SetObject

2013-04-12 Thread Orion Poplawski

New submission from Orion Poplawski:

I'm seeing a segfault running the scipy 0.12 tests against numpy 1.7.1 with 
python 3.3.1.  The crash is here:

test_ticket_1645 (test_lapack.TestRegression) ... 
Program received signal SIGSEGV, Segmentation fault.
PyErr_SetObject (exception=exception@entry=, 
value=value@entry='On entry to SGERQF parameter number 7 had an illegal 
value')
at /usr/src/debug/Python-3.3.1/Python/errors.c:67
67  exc_value = tstate->exc_value;
(gdb) print tstate
$1 = (PyThreadState *) 0x0

So it appears that PyThreadState_GET() is returning NULL and PyErr_SetOject() 
is not handling that condition.  Not sure if this is a sign of another issue.

(gdb) bt
#0  PyErr_SetObject (exception=exception@entry=, 
value=value@entry='On entry to SGERQF parameter number 7 had an illegal 
value')
at /usr/src/debug/Python-3.3.1/Python/errors.c:67
#1  0x77c93bbf in PyErr_SetString (exception=, 
string=string@entry=0x7fff8160 "On entry to SGERQF parameter number 7 
had an illegal value") at /usr/src/debug/Python-3.3.1/Python/errors.c:125
#2  0x7fffeea223f1 in xerbla_ (srname=, info=)
at numpy/linalg/python_xerbla.c:35
#3  0x7fffee4925d9 in sgerqf_ () from /usr/lib64/atlas/liblapack.so.3
#4  0x7fffe6d5a56f in f2py_rout__flapack_sgerqf ()
   from 
/scratch/orion/redhat/BUILDROOT/scipy-0.12.0-1.fc20.x86_64/usr/lib64/python3.3/site-packages/scipy/linalg/_flapack.cpython-33m.so
#5  0x77bda0cc in PyObject_Call (func=func@entry=, 
arg=arg@entry=(,), kw=kw@entry={'lwork': 
2})
at /usr/src/debug/Python-3.3.1/Objects/abstract.c:2082
#6  0x77c859b2 in ext_do_call (nk=, na=, 
flags=, pp_stack=0x7fff85f8, func=)
at /usr/src/debug/Python-3.3.1/Python/ceval.c:4406
#7  PyEval_EvalFrameEx (
f=f@entry=Frame 0x11ae310, for file /usr/lib64/python3.3/unittest/case.py, 
line 173, in handle 
(self=<_AssertRaisesContext(test_case=: 'assertMultiLineEqual', 
: 'assertListEqual', : 'assertDictEqual', : 
'assertTupleEqual', : 'assertSetEqual', : 'assertSetEqual'}) at remote 0x7fffecd1c390>, msg=None, 
obj_name='', expected=, 
expected_regex=None) at remote 0x7fffe0716cd0>, name='assertRaises', 
callable_obj=, args=(,), kwargs={'lwork': 2}), 
throwflag=throwflag@entry=0) at 
/usr/src/debug/Python-3.3.1/Python/ceval.c:2744
#8  0x77c879cc in fast_function (nk=, na=5, n=5, 
pp_stack=0x7fff8770, func=)
at /usr/src/debug/Python-3.3.1/Python/ceval.c:4179
#9  call_function (oparg=, pp_stack=0x7fff8770)
at /usr/src/debug/Python-3.3.1/Python/ceval.c:4112
..

it goes on a long ways down.

--
components: Interpreter Core
messages: 186684
nosy: opoplawski
priority: normal
severity: normal
status: open
title: Segfault in PyErr_SetObject
type: crash
versions: Python 3.3

___
Python tracker 
<http://bugs.python.org/issue17706>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue17706] Segfault in PyErr_SetObject

2013-04-15 Thread Orion Poplawski

Orion Poplawski added the comment:

Despite numpy not calling the library properly, it stills seems to me that 
python should not segfault due to not handling a null pointer.  But thanks for 
the help.

--

___
Python tracker 
<http://bugs.python.org/issue17706>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com