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", "copyright", "credits" or "license" for more information. #>>> import faulthandler #>>> faulthandler.enable() #>>> import numpy as np #>>> np.__version__ '1.9.0' #>>> import pandas as pd #>>> pd.__version__ '0.14.1' #>>> np.arange(pd.DatetimeIndex([])) Fatal Python error: Segmentation fault Current thread 0x00001d18: File "<stdin>", line 1 in <module> The exception dialog which pops up contains the following information: Unhandled exception at 0x000000000255EB49 (multiarray.pyd) in python.exe: 0xC0000005: Access violation reading location 0x0000000000000008. Thanks, Dave
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/numpy/numpy/pull/5225
Julian Taylor <jtaylor.debian <at> 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 report, this patch should fix it:
Thanks for the super-fast patch! Hopefully it will make it into the next bugfix release, even if it is an apparently little used functionality. -Dave
participants (2)
-
Dave Hirschfeld -
Julian Taylor