You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attaching gdb reveals the cause is the assumption that the dtype inferred from the attribute will also be structured:
>>> d = np.dtype(Bad)
Thread 1 "python3-dbg" received signal SIGSEGV, Segmentation fault.
PyArray_DescrFromTypeObject (type=type@entry=<type at remote 0x104a678>) at numpy/core/src/multiarray/scalarapi.c:479
479 Py_INCREF(new->names);
(gdb) p new->names
$1 = 0x0
(gdb)
eric-wieser
changed the title
BUG: subclasses of np.void can cause stack overflows
BUG: subclasses of np.void can cause a segfault
Oct 24, 2018
This gives a Deprecation warnign now (due to using the .dtype attribute). I am sure there are many others bugs around this, but this one appears not reproducible anymore.
The text was updated successfully, but these errors were encountered: