Re: [Numpy-discussion] Numpy intermittent seg fault

2015-12-13 Thread Jacopo Sabbatini
Filed the bug with OpenBlas (https://github.com/xianyi/OpenBLAS/issues/716) but they seem more inclined to think that something else corrupted the memory and the problem only shows up in OpenBlas. I have attached the backtrace for all the threads at the end. From preliminary investigation it seems

Re: [Numpy-discussion] Numpy intermittent seg fault

2015-12-11 Thread Antoine Pitrou
Hi, On Fri, 11 Dec 2015 10:05:59 +1000 Jacopo Sabbatini wrote: > > I'm experiencing random segmentation faults from numpy. I have generated a > core dumped and extracted a stack trace, the following: > > #0 0x7f3a8d921d5d in getenv () from /lib64/libc.so.6 > #1 0x7f3a843bde21 in blas

Re: [Numpy-discussion] Numpy intermittent seg fault

2015-12-10 Thread Nathaniel Smith
On Thu, Dec 10, 2015 at 4:05 PM, Jacopo Sabbatini wrote: > Hi, > > I'm experiencing random segmentation faults from numpy. I have generated a > core dumped and extracted a stack trace, the following: > > #0 0x7f3a8d921d5d in getenv () from /lib64/libc.so.6 > #1 0x7f3a843bde21 in blas_set

[Numpy-discussion] Numpy intermittent seg fault

2015-12-10 Thread Jacopo Sabbatini
Hi, I'm experiencing random segmentation faults from numpy. I have generated a core dumped and extracted a stack trace, the following: #0 0x7f3a8d921d5d in getenv () from /lib64/libc.so.6 #1 0x7f3a843bde21 in blas_set_parameter () from /opt/apps/sidescananalysis-9.7.1-42-gdd3e068+dev/li