Closed WebFreak001 closed 6 years ago
I have never tried using pyd on a pi. What compiler are you using?
ldc 1.6.0 (the arm release there)
I tried the ldc 1.1.1 deb package before which also had the same issue
which os?
Raspbian Stretch Lite from raspberry pi site on rpi 3 model B
don't call module_init. that's for python extensions (shared libraries)
nvm that comment, but well that still doesn't fix it
initial diagnosis: d thinks PyTypeObject.tp_flags' offset is 88, and c thinks it is 84. both agree on the previous field, tp_as_buffer, offset=80. d thinks tp_as_buffer's size is 4. A naive attempt at a reduced case didn't capture above behavior, which makes me suspect compiler bug. But it could be some linker configuration.
I noticed that on rpi 64 bit compilation still uses 32 bit size_t
filed ldc-developers/ldc#2456
@WebFreak001 try the raspibug branch. I have more environments to validate before it goes into master, but it should work for raspi.
yep that fixed it now, thanks
can you merge your change (I made a PR for you to easily do that) and release a new version?
when commenting out the init_rangewrapper function it seems to work, otherwise it segfaults:
it crashes on
py_init();