Re: [Numpy-discussion] segfault in np.arange

Julian Taylor googlemail.com> writes: > > On 23.10.2014 19:21, Dave Hirschfeld wrote: > > Hi, > > I accidentally passed a pandas DatetimeIndex to `np.arange` which caused > > it to segfault. It's a pretty dumb thing to do but I don't think it > > should cause a segfault! > > thanks for the r

Re: [Numpy-discussion] segfault in np.arange

On 23.10.2014 19:21, Dave Hirschfeld wrote: > Hi, > I accidentally passed a pandas DatetimeIndex to `np.arange` which caused > it to segfault. It's a pretty dumb thing to do but I don't think it > should cause a segfault! thanks for the report, this patch should fix it: https://github.com/nump

[Numpy-discussion] segfault in np.arange

Hi, I accidentally passed a pandas DatetimeIndex to `np.arange` which caused it to segfault. It's a pretty dumb thing to do but I don't think it should cause a segfault! Python 2.7.5 |Continuum Analytics, Inc.| (default, Jul 1 2013, 12:37:52) [MSC v.1500 64 bit (AMD64)] on win32 Type "help",

Re: [Numpy-discussion] segfault from scipy.io.netcdf with scipy-0.14 numpy-0.18

On 2014/05/07 11:26 PM, Robert McGibbon wrote: > Hey all, > > The travis tests for a library I work on just stopped working, and I > tracked down the bug to the following test case. The file > "MDTraj/testing/reference/mdcrd.nc " is a netcdf3 file > in our repository > (https://git

[Numpy-discussion] segfault from scipy.io.netcdf with scipy-0.14 numpy-0.18

Hey all, The travis tests for a library I work on just stopped working, and I tracked down the bug to the following test case. The file "MDTraj/testing/reference/mdcrd.nc" is a netcdf3 file in our repository ( https://github.com/rmcgibbo/mdtraj/tree/master/MDTraj/testing/reference). this script:

Re: [Numpy-discussion] Segfault with QR Decomposition

https://github.com/xianyi/OpenBLAS/issues/304 On 09.10.2013 17:24, Julian Taylor wrote: > yes thats probably openblas fault. > Openblas crashes all the time as soon as your matrices get bigger than a > couple of megabytes. > I'll investigate and report it upstream (as I have already far too often

Re: [Numpy-discussion] Segfault with QR Decomposition

yes thats probably openblas fault. Openblas crashes all the time as soon as your matrices get bigger than a couple of megabytes. I'll investigate and report it upstream (as I have already far too often for the exact same reason ...) On Wed, Oct 9, 2013 at 5:05 PM, Charanpal Dhanjal wrote: > Oops

[Numpy-discussion] Segfault with QR Decomposition

Oops, the second line should have been export OPENBLAS_NUM_THREADS=8 ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] Segfault with QR Decomposition

> >/ I get a segmentation fault upon running the following: > />/ > />/ import numpy > />/ A = numpy.ones((700, 8)) > />/ Q, R = numpy.linalg.qr(A) > />/ > />/ on Python 2.7.3, Linux 64-bit using numpy 1.9.0.dev-ec3603f linked > />/ against OpenBLAS. If A is a smaller matrix then the QR decompo

Re: [Numpy-discussion] Segfault with QR Decomposition

On Wed, Oct 9, 2013 at 8:04 AM, Charanpal Dhanjal wrote: > I get a segmentation fault upon running the following: > > import numpy > A = numpy.ones((700, 8)) > Q, R = numpy.linalg.qr(A) > > on Python 2.7.3, Linux 64-bit using numpy 1.9.0.dev-ec3603f linked > against OpenBLAS. If A is a smaller

[Numpy-discussion] Segfault with QR Decomposition

I get a segmentation fault upon running the following: import numpy A = numpy.ones((700, 8)) Q, R = numpy.linalg.qr(A) on Python 2.7.3, Linux 64-bit using numpy 1.9.0.dev-ec3603f linked against OpenBLAS. If A is a smaller matrix then the QR decomposition works (for example A has shape (40

[Numpy-discussion] Segfault for Numpy 1.4.1 on 64-bit CentOS-5

For library compatibility testing I'm trying to use numpy 1.4.1 with Python 2.7.3 on a 64-bit CentOS-5 platform. I installed a clean Python from source (basically "./configure --prefix=$prefix ; make install") and then installed numpy 1.4.1 with "python setup.py install". The crash message begins

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

On Tue, Jul 24, 2012 at 5:38 PM, Ondřej Čertík wrote: > Possible conclusion: > > I think I know what is going on. I use > > $ wine --version > wine-1.3.28 > > and it installs (by default) the following msvcr libraries: > > > $ ls ~/.wine/drive_c/windows/winsxs/ > manifests > Policies > x86_microso

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

Possible conclusion: I think I know what is going on. I use $ wine --version wine-1.3.28 and it installs (by default) the following msvcr libraries: $ ls ~/.wine/drive_c/windows/winsxs/ manifests Policies x86_microsoft.msxml2_6bd6b9abf345378f_4.1.0.0_none_deadbeef x86_microsoft.vc80.crt_1fc8b3

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

On Tue, Jul 24, 2012 at 5:04 PM, Ondřej Čertík wrote: > On Tue, Jul 24, 2012 at 3:58 PM, Ondřej Čertík > wrote: >> Ralf, >> David, what version of binutils do you use? I use 2.17.50 (https://github.com/certik/numpy-vendor) and maybe that's the problem, that the objdump from there

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

On Tue, Jul 24, 2012 at 3:58 PM, Ondřej Čertík wrote: > Ralf, > >>> David, what version of binutils do you use? >>> I use 2.17.50 (https://github.com/certik/numpy-vendor) >>> and maybe that's the problem, that the objdump from there >>> can't read the msvcr library. >>> >>> I use gcc 3.4.5. What e

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

Ralf, >> David, what version of binutils do you use? >> I use 2.17.50 (https://github.com/certik/numpy-vendor) >> and maybe that's the problem, that the objdump from there >> can't read the msvcr library. >> >> I use gcc 3.4.5. What exact version do you use in wine? >> > > I have gcc 3.4.5 and bin

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

On Tue, Jul 24, 2012 at 5:14 PM, Ondřej Čertík wrote: > On Fri, Jul 20, 2012 at 11:51 AM, David Cournapeau > wrote: > > On Thu, Jul 19, 2012 at 4:58 PM, Ondřej Čertík > wrote: > > > >> > >> So I have tried the MinGW-5.0.3.exe in Wine, but it tries to install > >> from some wrong url and it fails

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

On Fri, Jul 20, 2012 at 11:51 AM, David Cournapeau wrote: > On Thu, Jul 19, 2012 at 4:58 PM, Ondřej Čertík > wrote: > >> >> So I have tried the MinGW-5.0.3.exe in Wine, but it tries to install >> from some wrong url and it fails to install. >> I have unpacked the tarballs by hand into "~/.wine/d

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

On Thu, Jul 19, 2012 at 4:58 PM, Ondřej Čertík wrote: > > So I have tried the MinGW-5.0.3.exe in Wine, but it tries to install > from some wrong url and it fails to install. > I have unpacked the tarballs by hand into "~/.wine/drive_c/MinGW": > > binutils-2.17.50-20070129-1.tar.gz > w32api-3.7.ta

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

On Fri, Jul 20, 2012 at 12:24 PM, Ondřej Čertík wrote: >>> So I have tried the MinGW-5.0.3.exe in Wine, but it tries to install >>> from some wrong url and it fails to install. >>> I have unpacked the tarballs by hand into "~/.wine/drive_c/MinGW": >>> >> Not surprising, that MinGW is really gettin

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

>> So I have tried the MinGW-5.0.3.exe in Wine, but it tries to install >> from some wrong url and it fails to install. >> I have unpacked the tarballs by hand into "~/.wine/drive_c/MinGW": >> > Not surprising, that MinGW is really getting old. It's still the last > available one with gcc 3.x as II

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

On Thu, Jul 19, 2012 at 5:58 PM, Ondřej Čertík wrote: > On Thu, Jul 19, 2012 at 12:58 PM, Ondřej Čertík > wrote: > >>> I've nailed it to: > >>> > >> import numpy as np > >> np.array([complex(0, 1)], np.complex64) > >>> wine: Unhandled page fault on read access to 0x at address > >

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

On Thu, Jul 19, 2012 at 12:58 PM, Ondřej Čertík wrote: >>> I've nailed it to: >>> >> import numpy as np >> np.array([complex(0, 1)], np.complex64) >>> wine: Unhandled page fault on read access to 0x at address >>> (nil) (thread 0009), starting debugger... >>> ... > > Btw, I tried t

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

>> I've nailed it to: >> > import numpy as np > np.array([complex(0, 1)], np.complex64) >> wine: Unhandled page fault on read access to 0x at address >> (nil) (thread 0009), starting debugger... >> ... Btw, I tried to debug it using: $ winedbg --gdb "C:\Python27\python" and I got

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

On Thu, Jul 19, 2012 at 2:24 AM, Ondřej Čertík wrote: > Hi Ralf, > > On Wed, Jul 18, 2012 at 7:25 PM, Ralf Gommers > wrote: >> >> >> On Wed, Jul 18, 2012 at 1:24 PM, Ondřej Čertík >> wrote: >>> >>> Hi, >>> >>> I managed to compile NumPy in MinGW under Wine in Ubuntu 11.10 and >>> here is a full

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

Hi Ralf, On Wed, Jul 18, 2012 at 7:25 PM, Ralf Gommers wrote: > > > On Wed, Jul 18, 2012 at 1:24 PM, Ondřej Čertík > wrote: >> >> Hi, >> >> I managed to compile NumPy in MinGW under Wine in Ubuntu 11.10 and >> here is a full log of the tests: >> >> https://gist.github.com/3135607 >> >> It fails

Re: [Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

On Wed, Jul 18, 2012 at 1:24 PM, Ondřej Čertík wrote: > Hi, > > I managed to compile NumPy in MinGW under Wine in Ubuntu 11.10 and > here is a full log of the tests: > > https://gist.github.com/3135607 > > It fails at the test test_str (test_arrayprint.TestComplexArray) with > a segfault like this

[Numpy-discussion] Segfault in mingw in test_arrayprint.TestComplexArray

Hi, I managed to compile NumPy in MinGW under Wine in Ubuntu 11.10 and here is a full log of the tests: https://gist.github.com/3135607 It fails at the test test_str (test_arrayprint.TestComplexArray) with a segfault like this: test_str (test_arrayprint.TestComplexArray) ... wine: Unhandled pa

Re: [Numpy-discussion] segfault on searchsorted (1.6.2.dev-396dbb9)

On Tue, Jan 17, 2012 at 8:57 AM, Adam Klein wrote: > Hello, > > I get a segfault here: > > In [1]: x = np.array([1,2,3], dtype='M') > In [2]: x.searchsorted(2, side='left') > > But it's fine here: > > In [1]: x = np.array([1,2,3], dtype='M') > In [2]: x.view('i8').searchsorted(2, side='left') > O

[Numpy-discussion] segfault on searchsorted (1.6.2.dev-396dbb9)

Hello, I get a segfault here: In [1]: x = np.array([1,2,3], dtype='M') In [2]: x.searchsorted(2, side='left') But it's fine here: In [1]: x = np.array([1,2,3], dtype='M') In [2]: x.view('i8').searchsorted(2, side='left') Out[2]: 1 This segfaults again: x.view('i8').searchsorted(np.datetime64(

Re: [Numpy-discussion] Segfault for np.lookfor

Hi, On Sun, Aug 21, 2011 at 1:53 AM, Ben Walsh wrote: > > Hi > > My bad. Very sorry about that, guys. > > There's a patch for this here: > > https://github.com/walshb/numpy/tree/fix_np_lookfor_segv > > And I submitted a pull request. I'll add something to the tests too when I > have a little more

[Numpy-discussion] Segfault for np.lookfor

gt; > Message: 3 > Date: Tue, 16 Aug 2011 12:15:22 -0700 > From: Matthew Brett > Subject: Re: [Numpy-discussion] Segfault for np.lookfor > To: Discussion of Numerical Python > Message-ID: > > Content-Type: text/plain; charset=ISO-8859-1 > >> >> I opened t

Re: [Numpy-discussion] segfault on complex array on solaris x86

On Wed, Apr 13, 2011 at 8:50 AM, John Hunter wrote: > On Sat, Jan 15, 2011 at 7:28 AM, Ralf Gommers > wrote: >> I've opened http://projects.scipy.org/numpy/ticket/1713 so this doesn't get >> lost. > > Just wanted to bump this -- bug still exists in numpy HEAD 2.0.0.dev-fe3852f Just wanted to men

Re: [Numpy-discussion] Segfault for np.lookfor

Hi, On Tue, Aug 16, 2011 at 10:05 AM, Charles R Harris wrote: > > > On Mon, Aug 15, 2011 at 7:43 PM, Charles R Harris > wrote: >> >> >> On Mon, Aug 15, 2011 at 7:09 PM, Charles R Harris >> wrote: >>> >>> >>> On Mon, Aug 15, 2011 at 6:56 PM, Charles R Harris >>> wrote: On Mon, Au

Re: [Numpy-discussion] Segfault for np.lookfor

On Mon, Aug 15, 2011 at 7:43 PM, Charles R Harris wrote: > > > On Mon, Aug 15, 2011 at 7:09 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Mon, Aug 15, 2011 at 6:56 PM, Charles R Harris < >> charlesr.har...@gmail.com> wrote: >> >>> >>> >>> On Mon, Aug 15, 2011 at 3:53 PM

Re: [Numpy-discussion] Segfault for np.lookfor

On Mon, Aug 15, 2011 at 7:09 PM, Charles R Harris wrote: > > > On Mon, Aug 15, 2011 at 6:56 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Mon, Aug 15, 2011 at 3:53 PM, Matthew Brett >> wrote: >> >>> Hi, >>> >>> On current trunk, all tests pass but running the (forgive

Re: [Numpy-discussion] Segfault for np.lookfor

On Mon, Aug 15, 2011 at 6:56 PM, Charles R Harris wrote: > > > On Mon, Aug 15, 2011 at 3:53 PM, Matthew Brett wrote: > >> Hi, >> >> On current trunk, all tests pass but running the (forgive my language) >> doctests, I found this: >> >> In [1]: import numpy as np >> >> In [2]: np.__version__ >> Ou

Re: [Numpy-discussion] Segfault for np.lookfor

On Mon, Aug 15, 2011 at 3:53 PM, Matthew Brett wrote: > Hi, > > On current trunk, all tests pass but running the (forgive my language) > doctests, I found this: > > In [1]: import numpy as np > > In [2]: np.__version__ > Out[2]: '2.0.0.dev-730b861' > > In [3]: np.lookfor('cos') > Segmentation faul

[Numpy-discussion] Segfault for np.lookfor

Hi, On current trunk, all tests pass but running the (forgive my language) doctests, I found this: In [1]: import numpy as np In [2]: np.__version__ Out[2]: '2.0.0.dev-730b861' In [3]: np.lookfor('cos') Segmentation fault on: Linux angela 2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:07:17 U

Re: [Numpy-discussion] Segfault using "fromstring" and reading variable length string

On Fri, Apr 22, 2011 at 6:32 PM, Mark Wiebe wrote: > I took a quick look at this issue and committed a fix. PyArray_FromString > was doing a check to exclude object arrays, but that check was incorrect. > Now it should appropriately raise an exception instead of creating an > invalid array. > > >

Re: [Numpy-discussion] Segfault using "fromstring" and reading variable length string

On Fri, Apr 22, 2011 at 5:08 PM, Christoph Gohlke wrote: > > > On 4/22/2011 2:52 PM, Gökhan Sever wrote: > > > > > > On Fri, Apr 22, 2011 at 12:37 PM, Ralf Gommers > > mailto:ralf.gomm...@googlemail.com>> > wrote: > > > > On Thu, Apr 21, 2011 at 10:06 PM, Gökhan Sever > > mailto:gokhanse.

Re: [Numpy-discussion] Segfault using "fromstring" and reading variable length string

On 4/22/2011 2:52 PM, Gökhan Sever wrote: > > > On Fri, Apr 22, 2011 at 12:37 PM, Ralf Gommers > mailto:ralf.gomm...@googlemail.com>> wrote: > > On Thu, Apr 21, 2011 at 10:06 PM, Gökhan Sever > mailto:gokhanse...@gmail.com>> wrote: > > Hello, > > Given this piece of code (I can

Re: [Numpy-discussion] Segfault using "fromstring" and reading variable length string

On Fri, Apr 22, 2011 at 12:37 PM, Ralf Gommers wrote: > On Thu, Apr 21, 2011 at 10:06 PM, Gökhan Sever > wrote: > > Hello, > > Given this piece of code (I can provide the meg file off-the list for > those > > who wants to reproduce the error) > > Can you instead construct a test as simple as poss

Re: [Numpy-discussion] Segfault using "fromstring" and reading variable length string

On Thu, Apr 21, 2011 at 10:06 PM, Gökhan Sever wrote: > Hello, > Given this piece of code (I can provide the meg file off-the list for those > who wants to reproduce the error) Can you instead construct a test as simple as possible for this? It sounds like you need only a two line string to repro

[Numpy-discussion] Segfault using "fromstring" and reading variable length string

Hello, Given this piece of code (I can provide the meg file off-the list for those who wants to reproduce the error) import numpy as np f = open("a08A0122.341071.meg", "rb") dt = np.dtype([('line1', '|S80'), ('line2', np.object_), ('line3', '|S80'), ('line4', '|S80'), ('line5',

Re: [Numpy-discussion] segfault on complex array on solaris x86

On Sat, Jan 15, 2011 at 7:28 AM, Ralf Gommers wrote: > I've opened http://projects.scipy.org/numpy/ticket/1713 so this doesn't get > lost. Just wanted to bump this -- bug still exists in numpy HEAD 2.0.0.dev-fe3852f ___ NumPy-Discussion mailing list Num

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

Hi, On Tue, Mar 15, 2011 at 5:55 PM, Matthew Brett wrote: > Hi, > > On Tue, Mar 15, 2011 at 5:30 PM, Christoph Gohlke wrote: >> >> >> On 3/15/2011 5:13 PM, Matthew Brett wrote: >>> Hi, >>> >>> On Tue, Mar 15, 2011 at 10:23 AM, Matthew Brett   >>> wrote: Hi, On Tue, Mar 15, 2011 at

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

Hi, On Tue, Mar 15, 2011 at 5:30 PM, Christoph Gohlke wrote: > > > On 3/15/2011 5:13 PM, Matthew Brett wrote: >> Hi, >> >> On Tue, Mar 15, 2011 at 10:23 AM, Matthew Brett   >> wrote: >>> Hi, >>> >>> On Tue, Mar 15, 2011 at 10:12 AM, Pauli Virtanen  wrote: Tue, 15 Mar 2011 10:06:09 -0700, Mat

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

On 3/15/2011 5:13 PM, Matthew Brett wrote: > Hi, > > On Tue, Mar 15, 2011 at 10:23 AM, Matthew Brett > wrote: >> Hi, >> >> On Tue, Mar 15, 2011 at 10:12 AM, Pauli Virtanen wrote: >>> Tue, 15 Mar 2011 10:06:09 -0700, Matthew Brett wrote: Sorry to ask, and I ask partly because I'm in the mi

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

Hi, On Tue, Mar 15, 2011 at 10:23 AM, Matthew Brett wrote: > Hi, > > On Tue, Mar 15, 2011 at 10:12 AM, Pauli Virtanen wrote: >> Tue, 15 Mar 2011 10:06:09 -0700, Matthew Brett wrote: >>> Sorry to ask, and I ask partly because I'm in the middle of a py3k port, >>> but is this the right fix to this

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

On 3/15/2011 11:34 AM, Christoph Gohlke wrote: > > > On 3/15/2011 10:12 AM, Pauli Virtanen wrote: >> Tue, 15 Mar 2011 10:06:09 -0700, Matthew Brett wrote: >>> Sorry to ask, and I ask partly because I'm in the middle of a py3k port, >>> but is this the right fix to this problem? I was confused by

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

On 3/15/2011 10:12 AM, Pauli Virtanen wrote: > Tue, 15 Mar 2011 10:06:09 -0700, Matthew Brett wrote: >> Sorry to ask, and I ask partly because I'm in the middle of a py3k port, >> but is this the right fix to this problem? I was confused by the >> presence of the old PyString_AsString function.

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

Hi, On Tue, Mar 15, 2011 at 11:07 AM, Pauli Virtanen wrote: > Tue, 15 Mar 2011 10:23:35 -0700, Matthew Brett wrote: > [clip] >> OK - I realize I'm being very lazy here but, do you mean: >> >>         PyErr_Format(PyExc_ValueError,                      "field named %s not found.",      

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

Tue, 15 Mar 2011 10:23:35 -0700, Matthew Brett wrote: [clip] > OK - I realize I'm being very lazy here but, do you mean: > > PyErr_Format(PyExc_ValueError, >>> "field named %s not found.", >>> PyString_AsString(PyObject_Repr(index))); > >> The PyS

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

On Tue, Mar 15, 2011 at 11:12 AM, Pauli Virtanen wrote: > Tue, 15 Mar 2011 10:06:09 -0700, Matthew Brett wrote: > > Sorry to ask, and I ask partly because I'm in the middle of a py3k port, > > but is this the right fix to this problem? I was confused by the > > presence of the old PyString_AsStr

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

Hi, On Tue, Mar 15, 2011 at 10:12 AM, Pauli Virtanen wrote: > Tue, 15 Mar 2011 10:06:09 -0700, Matthew Brett wrote: >> Sorry to ask, and I ask partly because I'm in the middle of a py3k port, >> but is this the right fix to this problem?  I was confused by the >> presence of the old PyString_AsSt

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

Tue, 15 Mar 2011 10:06:09 -0700, Matthew Brett wrote: > Sorry to ask, and I ask partly because I'm in the middle of a py3k port, > but is this the right fix to this problem? I was confused by the > presence of the old PyString_AsString function. It's not a correct fix. The original code seems als

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

Hi, On Sun, Mar 13, 2011 at 12:07 PM, Matthew Brett wrote: > Hi, > > On Sun, Mar 13, 2011 at 11:51 AM, Christoph Gohlke wrote: >> >> >> On 3/13/2011 11:29 AM, Matthew Brett wrote: >>> >>> Hi >>> >>> On Sun, Mar 13, 2011 at 9:54 AM, Christoph Gohlke  wrote: On 3/13/2011 1:57 AM, Matthew

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

On Sun, Mar 13, 2011 at 12:51 PM, Christoph Gohlke wrote: > > > On 3/13/2011 11:29 AM, Matthew Brett wrote: > > Hi > > > > On Sun, Mar 13, 2011 at 9:54 AM, Christoph Gohlke > wrote: > >> On 3/13/2011 1:57 AM, Matthew Brett wrote: > >>> Hi, > >>> I have this on my OSX 10.6 system and numpy 1.5.1

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

Hi, On Sun, Mar 13, 2011 at 11:51 AM, Christoph Gohlke wrote: > > > On 3/13/2011 11:29 AM, Matthew Brett wrote: >> >> Hi >> >> On Sun, Mar 13, 2011 at 9:54 AM, Christoph Gohlke  wrote: >>> >>> On 3/13/2011 1:57 AM, Matthew Brett wrote: Hi, I have this on my OSX 10.6 system and nump

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

On 3/13/2011 11:29 AM, Matthew Brett wrote: > Hi > > On Sun, Mar 13, 2011 at 9:54 AM, Christoph Gohlke wrote: >> On 3/13/2011 1:57 AM, Matthew Brett wrote: >>> Hi, >>> I have this on my OSX 10.6 system and numpy 1.5.1 and current numpy >>> head (30ee1d352): >>> >>> $ python3.2 >>> Python 3.2 (r3

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

Hi On Sun, Mar 13, 2011 at 9:54 AM, Christoph Gohlke wrote: > On 3/13/2011 1:57 AM, Matthew Brett wrote: >> Hi, >> I have this on my OSX 10.6 system and numpy 1.5.1 and current numpy >> head (30ee1d352): >> >> $ python3.2 >> Python 3.2 (r32:88452, Feb 20 2011, 11:12:31) >> [GCC 4.2.1 (Apple Inc.

Re: [Numpy-discussion] Segfault with python 3.2 structured array non-existent field

On 3/13/2011 1:57 AM, Matthew Brett wrote: > Hi, > > I have this on my OSX 10.6 system and numpy 1.5.1 and current numpy > head (30ee1d352): > > $ python3.2 > Python 3.2 (r32:88452, Feb 20 2011, 11:12:31) > [GCC 4.2.1 (Apple Inc. build 5664)] on darwin > Type "help", "copyright", "credits" or "li

[Numpy-discussion] Segfault with python 3.2 structured array non-existent field

Hi, I have this on my OSX 10.6 system and numpy 1.5.1 and current numpy head (30ee1d352): $ python3.2 Python 3.2 (r32:88452, Feb 20 2011, 11:12:31) [GCC 4.2.1 (Apple Inc. build 5664)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import numpy as np >>> a = n

Re: [Numpy-discussion] segfault on complex array on solaris x86

I've opened http://projects.scipy.org/numpy/ticket/1713 so this doesn't get lost. Ralf On Thu, Jan 6, 2011 at 12:27 AM, John Hunter wrote: > johnh@udesktop253:~> gcc --version > gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath) > Copyright (C) 2004 Free Software Foundation, Inc. > This is free

[Numpy-discussion] segfault on complex array on solaris x86

jo...@udesktop253:~> gcc --version gcc (GCC) 3.4.3 (csl-sol210-3_4-branch+sol_rpath) Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. jo...@udeskt

[Numpy-discussion] segfault in vdot

http://projects.scipy.org/numpy/ticket/1335 ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Segfault when using scipy.special.hermite?

ke, 2009-10-28 kello 14:21 +0100, Ole Streicher kirjoitti: > Is there something wrong with scipy.special.hermite? The following > code produces glibc errors: It's probably this issue: http://projects.scipy.org/numpy/ticket/1211 The most likely cause is that the linear algebra libraries (

Re: [Numpy-discussion] Segfault when using scipy.special.hermite?

that code works fine for me: ubuntu 9.04 x64 python 2.6.2 scipy 0.7.1 numpy 1.3.0 ipython 0.9.1 On Wed, Oct 28, 2009 at 2:21 PM, Ole Streicher wrote: > Hi, > > Is there something wrong with scipy.special.hermite? The following code > produces glibc errors: > > 8<-

[Numpy-discussion] Segfault when using scipy.special.hermite?

Hi, Is there something wrong with scipy.special.hermite? The following code produces glibc errors: 8<--- import scipy.special h = [] for i in xrange(15): print i h.append(scipy.special.hermite(i+1)) 8<--- results in ... 12 *

Re: [Numpy-discussion] Segfault with dotblas on OS X 10.5.5/PPC (but not on Intel?)

On 12-Nov-08, at 8:18 PM, David Cournapeau wrote: > On Wed, 2008-11-12 at 19:24 -0500, David Warde-Farley wrote: > >> >> Indeed, for the size of problem I *thought* I was running, 32 bit >> would be sufficient. In fact I had my data transposed and so was >> working with a much larger matrix which

Re: [Numpy-discussion] Segfault with dotblas on OS X 10.5.5/PPC (but not on Intel?)

On Wed, 2008-11-12 at 19:24 -0500, David Warde-Farley wrote: > > Indeed, for the size of problem I *thought* I was running, 32 bit > would be sufficient. In fact I had my data transposed and so was > working with a much larger matrix which would put me past the 32-bit > bound. Still, ideal

Re: [Numpy-discussion] Segfault with dotblas on OS X 10.5.5/PPC (but not on Intel?)

On 12-Nov-08, at 6:05 PM, Michael Abshoff wrote: >> I'm running the python.org 2.5.2 build of Python, and the latest SVN >> build of numpy (though the same thing happened with 1.1.0). > > IIRC that is a universal build for 32 bit PPC and Intel, so > depending on > the problem size 32 bits might

Re: [Numpy-discussion] Segfault with dotblas on OS X 10.5.5/PPC (but not on Intel?)

David Warde-Farley wrote: > Hello folks, Hi David, > I'm doing some rather big matrix products on a G5, and ran into this. > Strangely on the same OS version on my Intel laptop, this isn't an > issue. Available memory isn't the problem either, I don't think, this > machine is pretty beefy.

[Numpy-discussion] Segfault with dotblas on OS X 10.5.5/PPC (but not on Intel?)

Hello folks, I'm doing some rather big matrix products on a G5, and ran into this. Strangely on the same OS version on my Intel laptop, this isn't an issue. Available memory isn't the problem either, I don't think, this machine is pretty beefy. I'm running the python.org 2.5.2 build of Pyth

Re: [Numpy-discussion] Segfault in PyArray_Item_XDECREF when using recarray object references titles

I've filed a bug, with a patch to address all these issues, here: http://scipy.org/scipy/numpy/ticket/877 Cheers, Mike Michael Droettboom wrote: > I also noticed that the inverse operation, PyArray_Item_INCREF has the > potential to leak memory as it will doubly-increment each object in the >

Re: [Numpy-discussion] Segfault in PyArray_Item_XDECREF when using recarray object references titles

I also noticed that the inverse operation, PyArray_Item_INCREF has the potential to leak memory as it will doubly-increment each object in the array. The solution there probably isn't quite as clean, since we can't just mark the pointer. It will have to somehow avoid incref'ing the objects tw

[Numpy-discussion] Segfault in PyArray_Item_XDECREF when using recarray object references titles

I've run into a segfault that occurs in the array destructor with arrays containing object references with both names and titles. When a field contains both and name and a title, the fields dictionary contains two entries for that field. This means that the array item destructor (which iterat

Re: [Numpy-discussion] segfault problem with numpy and pickle

I have added a valgrind report to bug 551. The report indicates a problem with uninitialized values. The segfault does seem to be related to certain configurations of atlas. I can confirm that I had this same problem occurs with the Ubuntu 7.04 installed scipy with SSE2 optimized ATLAS.

Re: [Numpy-discussion] segfault problem with numpy and pickle

I think you are right. This does seem to be the same bug as 551. I will try a non optimized ATLAS to see if that helps. ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] segfault problem with numpy and pickle

to, 2008-01-24 kello 13:18 -0700, David Bolme kirjoitti: > A am having some trouble when pickling numpy arrays. Basically I use > one python script to create the array and then pickle it. When I load > the pickled array using a different python script it appears to load > fine. When I try to pe

Re: [Numpy-discussion] segfault problem with numpy and pickle

Hi David On Thu, Jan 24, 2008 at 01:18:45PM -0700, David Bolme wrote: > A am having some trouble when pickling numpy arrays. Basically I use one > python script to create the array and then pickle it. When I load the pickled > array using a different python script it appears to load fine. When

[Numpy-discussion] segfault problem with numpy and pickle

A am having some trouble when pickling numpy arrays. Basically I use one python script to create the array and then pickle it. When I load the pickled array using a different python script it appears to load fine. When I try to perform a matrix multiply on the array with a vector (using

Re: [Numpy-discussion] segfault with atlas3-sse2, works with atlas3-sse

On Dec 21, 2007 9:40 AM, Charles R Harris <[EMAIL PROTECTED]> wrote: > > > > > On Dec 20, 2007 9:32 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote: > > > > when compiled on Debian, numpy segfaults when used with ATLAS sse2, > > > > but works when used against ATLAS sse. More information here: > > > >

Re: [Numpy-discussion] segfault with atlas3-sse2, works with atlas3-sse

On Dec 20, 2007 9:32 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote: > > > when compiled on Debian, numpy segfaults when used with ATLAS sse2, > > > but works when used against ATLAS sse. More information here: > > > > What is the machine on which you are getting the segfault? Is it > > I don't know

Re: [Numpy-discussion] segfault with atlas3-sse2, works with atlas3-sse

to, 2007-12-20 kello 17:32 +0100, Ondrej Certik kirjoitti: > > > when compiled on Debian, numpy segfaults when used with ATLAS sse2, > > > but works when used against ATLAS sse. More information here: > > > > What is the machine on which you are getting the segfault? Is it > > I don't know which

Re: [Numpy-discussion] segfault with atlas3-sse2, works with atlas3-sse

> > when compiled on Debian, numpy segfaults when used with ATLAS sse2, > > but works when used against ATLAS sse. More information here: > > What is the machine on which you are getting the segfault? Is it I don't know which machine the reporter of this bug in Debian uses, but I use Intel Core D

Re: [Numpy-discussion] segfault with atlas3-sse2, works with atlas3-sse

Hi, > when compiled on Debian, numpy segfaults when used with ATLAS sse2, > but works when used against ATLAS sse. More information here: What is the machine on which you are getting the segfault? Is it possible you are trying to run SSE2 instructions on a machine without SSE2? Best, Matthew _

[Numpy-discussion] segfault with atlas3-sse2, works with atlas3-sse

Hi, when compiled on Debian, numpy segfaults when used with ATLAS sse2, but works when used against ATLAS sse. More information here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448530 I have no idea, where the problem is. Do you have any ideas, what we should try? Thanks a lot, Ondrej ___

Re: [Numpy-discussion] SegFault/double free with simple array mask operation

On Sun, Nov 18, 2007 at 11:18:10AM -1000, Eric Firing wrote: > Ticket #607 should be closed now also. It looks like I can't do that, > even though I created the ticket. > > I'm not sure whether it was the fix for #614 that did it, or whether it > is the code it referred to, but now a proper exc

Re: [Numpy-discussion] SegFault/double free with simple array mask operation

Stefan, Ticket #607 should be closed now also. It looks like I can't do that, even though I created the ticket. I'm not sure whether it was the fix for #614 that did it, or whether it is the code it referred to, but now a proper exception is raised instead of a segfault. Eric Stefan van der

Re: [Numpy-discussion] SegFault/double free with simple array mask operation

On Sat, Nov 17, 2007 at 12:55:57PM +0100, Achim Gaedke wrote: > Achim Gaedke wrote: > > David Cournapeau wrote: > > > >> Could you open a ticket on the numpy trac system ? (I can confirm the bug) > >> > >> cheers, > >> > >> David > >> > >> > > It is Ticket #614 . The version information

Re: [Numpy-discussion] segfault with dot

2007/11/17, Jesus Torrecilla Pinero <[EMAIL PROTECTED]>: > > numpy-1.0.4.win32-py2.5 from sourceforge (precompiled binary) > CPU: AMD Athlon XP 2600+ > 2.09 GHz, 1.00 Gb RAM > The error report says: > AppName: pythonw.exe AppVer: 0.0.0.0 ModName: _dotblas.pyd > ModVer: 0.0.0.0

Re: [Numpy-discussion] segfault with dot

numpy-1.0.4.win32-py2.5 from sourceforge (precompiled binary) CPU: AMD Athlon XP 2600+ 2.09 GHz, 1.00 Gb RAM The error report says: AppName: pythonw.exe AppVer: 0.0.0.0 ModName: _dotblas.pyd ModVer: 0.0.0.0 Offset: 0007ecf3 Jesús Torrecilla Pinero ___

Re: [Numpy-discussion] SegFault/double free with simple array mask operation

Achim Gaedke wrote: > David Cournapeau wrote: > >> Could you open a ticket on the numpy trac system ? (I can confirm the bug) >> >> cheers, >> >> David >> >> > It is Ticket #614 . The version information in trac are outdated, I > could not select version 1.0.3 or 1.0.4 . > Here is th

Re: [Numpy-discussion] segfault with dot

What CPU do you have and which version of numpy did you get and where did you get it from ? Matthieu 2007/11/17, Jesus Torrecilla Pinero <[EMAIL PROTECTED]>: > > I am using Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) under Windows > XP and converting a program from Numeric to Numpy. If I hav

[Numpy-discussion] segfault with dot

I am using Python 2.5.1 (r251:54863, Apr 18 2007, 08:51:08) under Windows XP and converting a program from Numeric to Numpy. If I have two arrays, say K and T and do dot(K,T) or K*T everything goes well, but if I have a vector b and try dot(K,b) or K*b I get a segfault. I have tried to run the tes

Re: [Numpy-discussion] SegFault/double free with simple array mask operation

David Cournapeau wrote: > Achim Gaedke wrote: > >> Hello everybody! >> >> Please have a look at the program below: >> >> # start >> import numpy >> >> t_array=numpy.ones(2048, dtype=numpy.float32) >> sinc_array=numpy.array((len(t_array),),dtype=numpy.float32) >> sinc_array[(t_array > 0.)]=1.0 >>

Re: [Numpy-discussion] SegFault/double free with simple array mask operation

Achim Gaedke wrote: > Hello everybody! > > Please have a look at the program below: > > # start > import numpy > > t_array=numpy.ones(2048, dtype=numpy.float32) > sinc_array=numpy.array((len(t_array),),dtype=numpy.float32) > sinc_array[(t_array > 0.)]=1.0 > # end > > If you execute this program, it

  1   2   >