Charles R Harris <charlesr.harris <at> gmail.com> writes: > > > On Thu, Apr 12, 2012 at 8:13 PM, Charles R Harris <charlesr.harris <at> gmail.com> wrote: > > On Thu, Apr 12, 2012 at 7:41 PM, Charles R Harris <charlesr.harris <at> gmail.com> wrote: > > On Thu, Apr 12, 2012 at 2:05 AM, Chris Ball <ceball <at> gmail.com> wrote: > > > > Hi, > I'm trying out various continuous integration options, so I happen to be > testing NumPy on several platforms that I don't normally use. > Recently, I've been getting a segmentation fault on Debian 6 (with Python > 2.7.2): > Linux debian6-amd64 2.6.32-5-amd64 #1 SMP Thu Mar 22 17:26:33 UTC 2012 x86_64 > GNU/Linux (Debian GNU/Linux 6.0 \n \l) ... > Segmentation fault is buried in console output of Jenkins:https:// jenkins.shiningpanda.com/scipy/job/NumPy/PYTHON=CPython-2.7/6/console > The previous build was ok:https://jenkins.shiningpanda.com/scipy/job/NumPy/ PYTHON=CPython-2.7/5/console > Changes that Jenkins claims are responsible:https://jenkins.shiningpanda.com/ scipy/job/NumPy/PYTHON=CPython-2.7/6/ > changes#detail0 > > > > It seems that python2.7 is far, far, too recent to be part of Debian 6. I mean, finding python 2.7 in recent Debian stable would be like finding an atomic cannon in a 1'st dynasty Egyptian tomb. So it is in testing, but for replication I like to know where you got it. > > > > > > Python 2.7 from Debian testing works fine here. > > > > > But ActiveState python (ucs2) segfaults with>>> a = np.array(['0123456789'], 'U') > >>> aSegmentation faultThe string needs to be long for this to show.Chuck
Sorry for the delay. I'll let you know about that as soon as I can (I didn't set up the machine, and although I can get ssh access, it's not straightforward). Chris _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion