-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
Passing MagicMock to np.dtype causes a segmentation fault #12982
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Could you post the backtrace? |
@charris I'm not very familiar with gdb. How do I do that? |
|
Thanks! See below.
(venv3) vagrant: 14:57:27 numpy$ gdb --args python runtests.py -g --python mytest.py
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from python...(no debugging symbols found)...done.
(gdb) break array_empty_like
Function "array_empty_like" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (array_empty_like) pending.
(gdb) run
Starting program: /home/vagrant/numpy/venv3/bin/python runtests.py -g --python mytest.py
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Building, see build.log...
Build OK
Enabling display of all warnings
Program received signal SIGSEGV, Segmentation fault. |
The code path in scalarapi.c which checks dtype on one inheriting from np.void is especially awkward and was completely untested previously. So I am not sure we should even support it at all. Closes numpygh-12982, numpygh-3614, and numpygh-12751
The code path in scalarapi.c which checks dtype on one inheriting from np.void is especially awkward and was completely untested previously. So I am not sure we should even support it at all. Closes numpygh-12982, numpygh-3614, and numpygh-12751
The code path in scalarapi.c which checks dtype on one inheriting from np.void is especially awkward and was completely untested previously. So I am not sure we should even support it at all. Closes numpygh-12982, numpygh-3614, and numpygh-12751
Passing MagicMock to np.dtype causes a segmentation fault. Original issue raised in Pandas
Reproducing code example:
Error message:
Numpy/Python version information:
The text was updated successfully, but these errors were encountered: