https://github.com/numpy/numpy/issues/7545
On Wed, Apr 13, 2016 at 3:38 PM, Nathaniel Smith <n...@pobox.com> wrote:
> I can reproduce in self-compiled 1.9, so it's not a new bug.
>
> I think something's going wrong with NPY_SIGINT_ON / NPY_SIGINT_OFF,
> where our special sigint handler is getting left in place even after
> our code finishes running.
>
> Skimming the code, my best guess is that this is due to a race
> condition in how we save/restore the original signal handler, when
> multiple threads are running numpy fftpack code at the same time (and
> thus using NPY_SIGINT_{ON,OFF} from multiple threads).
>
> -n
>
> On Wed, Apr 13, 2016 at 1:47 PM, Matthew Brett <matthew.br...@gmail.com>
> wrote:
>> On Wed, Apr 13, 2016 at 1:29 PM, Oscar Benjamin
>> <oscar.j.benja...@gmail.com> wrote:
>>> On 13 April 2016 at 20:15, Matthew Brett <matthew.br...@gmail.com> wrote:
>>>> Done. If y'all are on linux, and you have pip >= 8.11, you should
>>>> now see this kind of thing:
>>>
>>> That's fantastic. Thanks Matt!
>>>
>>> I just test installed this and ran numpy.test(). All tests passed but
>>> then I got a segfault at the end by (semi-accidentally) hitting Ctrl-C
>>> at the prompt:
>>>
>>> $ python
>>> Python 2.7.9 (default, Apr 2 2015, 15:33:21)
>>> [GCC 4.9.2] on linux2
>>> Type "help", "copyright", "credits" or "license" for more information.
>>>>>> import numpy
>>>>>> numpy.test()
>>> Running unit tests for numpy
>>> <snip>
>>> Ran 5781 tests in 72.238s
>>>
>>> OK (KNOWNFAIL=6, SKIP=15)
>>> <nose.result.TextTestResult run=5781 errors=0 failures=0>
>>>>>> Segmentation fault (core dumped)
>>>
>>> It was stopped at the prompt and then I did Ctrl-C and then the
>>> seg-fault message.
>>>
>>> $ uname -a
>>> Linux vnwulf 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC
>>> 2015 x86_64 x86_64 x86_64 GNU/Linux
>>> $ lsb_release -a
>>> No LSB modules are available.
>>> Distributor ID: Ubuntu
>>> Description: Ubuntu 15.04
>>> Release: 15.04
>>> Codename: vivid
>>>
>>
>> Thanks so much for testing - that's very useful.
>>
>> I get the same thing on my Debian Sid machine.
>>
>> Actually I also get the same thing with a local compile against Debian
>> ATLAS, here's the stack trace after:
>>
>>>>> import numpy; numpy.test()
>>>>> # Ctrl-C
>>
>> https://gist.github.com/f6d8fb42f24689b39536a2416d717056
>>
>> Do you get this as well?
>>
>> Cheers,
>>
>> Matthew
>> _______________________________________________
>> NumPy-Discussion mailing list
>> NumPy-Discussion@scipy.org
>> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>
>
> --
> Nathaniel J. Smith -- https://vorpus.org
--
Nathaniel J. Smith -- https://vorpus.org
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion
