This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author weeble
Recipients weeble
Date 2014-08-28.22:02:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1409263351.06.0.346178904757.issue22273@psf.upfronthosting.co.za>
In-reply-to
Content
I had a closer look at the cif object in gdb. The ffi_type of the argument in question has size 16, alignment 1, type FFI_TYPE_STRUCT and elements contains a single nested ffi_type, of size 8, alignment 8, type FFI_TYPE_POINTER.

I think this pointer type is wrong. The struct should indeed be size 16, but its contents (in this case) should be 16 bytes of uint8s, rather than a single pointer. I'm not certain how to correctly describe an array to libffi. While you might be able to hack it with a nested struct filled with 16 individual integers, I have no idea if that would work consistently across platforms.
History
Date User Action Args
2014-08-28 22:02:31weeblesetrecipients: + weeble
2014-08-28 22:02:31weeblesetmessageid: <1409263351.06.0.346178904757.issue22273@psf.upfronthosting.co.za>
2014-08-28 22:02:31weeblelinkissue22273 messages
2014-08-28 22:02:31weeblecreate