[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

[issue17706] Segfault in PyErr_SetObject

2013-04-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: Thank you, closing then. -- resolution: -> invalid status: open -> closed ___ Python tracker ___ __

[issue17706] Segfault in PyErr_SetObject

2013-04-13 Thread Pauli Virtanen
Pauli Virtanen added the comment: Yes, this is a bug in numpy.linalg --- the GIL is released but the error handling code assumes it's not. The error doesn't appear with in typical LAPACK installations, so this code branch was missed. -- nosy: +pv __

[issue17706] Segfault in PyErr_SetObject

2013-04-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: What is xerbla? PyThreadState_GET() returning NULL means the GIL has been released, sounds like a bug in a third-party C extension. -- nosy: +pitrou ___ Python tracker ___

[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=,