[Numpy-discussion] Current SVN segfaults under VC7
mfmorss at aep.com
mfmorss at aep.com
Thu Mar 23 09:05:03 EST 2006
Oh for the days of imperative programming!
y=f(x,...)
x=f(x,...)
was just too easy, I guess.
Mark F. Morss
Principal Analyst, Market Risk
American Electric Power
Travis Oliphant
<oliphant.travis@
ieee.org> To
Sent by: numpy-discussion
numpy-discussion- <numpy-discussion at lists.sourceforge
admin at lists.sourc .net>
eforge.net cc
Subject
03/22/2006 10:06 Re: [Numpy-discussion] Current SVN
PM segfaults under VC7
Tim Hochberg wrote:
>
> OK, now that I've got things working, I can report a real segfault
> under VC7. The following snippet of code:
>
> from numpy import *
> a = arange(100.)
> b = array(1+1j)
> (a+1) ** (b+3)
I can reproduce it on Linux. It looks like it's related to the power
optimization stuff that was recently checked in. power(a,b+3) does not
crash but
>>> a**(b+3)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1076248704 (LWP 1545)]
0x404162df in array_power_is_scalar (o2=0x8294200, exp=0xbfffec68)
at arrayobject.c:2656
2656 arrayobject.c: No such file or directory.
in arrayobject.c
-Travis
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Numpy-discussion mailing list
Numpy-discussion at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion
More information about the NumPy-Discussion
mailing list