Skip to content
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

segfault with non-native endian memoryview in python 3.4b1 #4138

Closed
rgommers opened this issue Dec 23, 2013 · 0 comments
Closed

segfault with non-native endian memoryview in python 3.4b1 #4138

rgommers opened this issue Dec 23, 2013 · 0 comments

Comments

@rgommers
Copy link
Member

I don't get a traceback for this one. Works fine with python 3.3, raises ValueError like it's supposed to.

>>> assert sys.byteorder == 'little'
>>> x = np.array([1, 2, 3], dtype='>q')
>>> x = memoryview(x)

Printed to stdout:

python3.4: Python/ceval.c:4257: call_function: Assertion `(x != ((void *)0) && 
!PyErr_Occurred()) || (x == ((void *)0) && PyErr_Occurred())' failed.
Aborted (core dumped)

32-bit linux, python3.4b1 debug build, gcc 4.8.1.

The above is a simplified version of a test that crashes when running the test suite: TestNewBufferProtocol.test_roundtrip from test_multiarray.py.

Maybe someone familiar with memoryview can easily tell if this is a numpy or a python issue?

@pv pv closed this as completed in 5733037 Jan 8, 2014
juliantaylor added a commit to juliantaylor/numpy that referenced this issue Jan 8, 2014
late return triggers an assert with python3.4 in debug mode.
Closes numpygh-4138.
juliantaylor added a commit to juliantaylor/numpy that referenced this issue Jan 8, 2014
late return triggers an assert with python3.4 in debug mode.
Closes numpygh-4138.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant