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
Issue with concatenating structured arrays (segmentation fault) (Trac #2084) #2676
Comments
trac user lcampagn wrote on 2012-09-24 I can confirm this bug and reproduce the segmentation fault:
I've run into this crash in a few different instances. |
Title changed from |
I think this has to do with the TODO at
At least, this is the ultimate failure in this issue. |
I've not been able to reproduce the segfault. I've also dug into this enough to realize that the ultimate issue here is asking NumPy to combine arbitrary structured arrays is more complicated than asking it to combine strings. This issue presents a case where the combination is obvious to the eye, but it's not clear how NumPy should merge arbitrary structured arrays (assume fields with the same name are to be combined? take the union of what remains?). Since I'm new to this project, I'll leave this open for now, and try to find somewhere else to direct my efforts :-P. |
Well, it should not segfault. We should raise an error until something if figured out. |
Yeah--it is raising an error now. I couldn't get it to segfault. |
@charris: Any chance this issue could be reopened? At least in the case where the field names all match and are in the same order, I think it is clear that the result should have these same field names in this order and each field should use the result of promoting the corresponding types. |
Original ticket http://projects.scipy.org/numpy/ticket/2084 on 2012-03-19 by @astrofrog, assigned to unknown.
The following demonstrates the issue - even though Numpy knows how to concatenate the fields of a structured array, it crashes if one tries to concatenate the structured arrays themselves:
A similar issue occurs with floating-point values of different endian-ness:
In some cases, this can even cause segmentation faults, though I have yet to find a way to reproduce this consistently.
The text was updated successfully, but these errors were encountered: