Python - Ctypes CFUNCTYPE crashes in ARM devices
up vote
1
down vote
favorite
I'm trying to register a python callback to be called from my C code using Ctypes. Everything works fine on my computer, but python crashes when the code runs in an ARM device.
In my computer I'm using python 3.6.6 and this ARM device uses python 3.6.3. I'm using buildroot to generate the images.
Well, after some tests seems that the problem is related to CFUNCTYPE.
The following code only test the CFUNCTYPE, and it runs on my computer but crashes (segmentation fault) on the ARM device:
from ctypes import *
def func():
print("func called")
CALLBACK = CFUNCTYPE(None)
callback = CALLBACK(func)
print("Calling callback")
callback()
print("Done!")
The result in my computer is:
Calling callback
func called
Done!
The result in the ARM device is:
Calling callback
Segmentation fault
Is this a bug in CFUNCTYPE? Or I need to do something different? I'm running a lot of python code in this device and everything runs fine, except this CFUNCTYPE.
Thanks
python callback crash ctypes buildroot
asked Nov 21 at 16:37
Dgdiniz
83
add a comment |
up vote
1
down vote
favorite
I'm trying to register a python callback to be called from my C code using Ctypes. Everything works fine on my computer, but python crashes when the code runs in an ARM device.
In my computer I'm using python 3.6.6 and this ARM device uses python 3.6.3. I'm using buildroot to generate the images.
Well, after some tests seems that the problem is related to CFUNCTYPE.
The following code only test the CFUNCTYPE, and it runs on my computer but crashes (segmentation fault) on the ARM device:
from ctypes import *
def func():
print("func called")
CALLBACK = CFUNCTYPE(None)
callback = CALLBACK(func)
print("Calling callback")
callback()
print("Done!")
The result in my computer is:
Calling callback
func called
Done!
The result in the ARM device is:
Calling callback
Segmentation fault
Is this a bug in CFUNCTYPE? Or I need to do something different? I'm running a lot of python code in this device and everything runs fine, except this CFUNCTYPE.
Thanks
python callback crash ctypes buildroot
asked Nov 21 at 16:37
Dgdiniz
83
FYI, this works calling the callback on Windows with both 32- and 64-bit Pythons. I normally only call callbacks like this from C but calling from Python works on Intel architecture. Seems like a bug.
– Mark Tolonen
Nov 22 at 2:17
Yes, seems like a bug. I'll also call this from C. This is only a short example to activate the bug. I found an alternative solution using Cython. I created a cython file between my python and C code. This way I can register the callbacks in a similar way.
– Dgdiniz
Nov 23 at 3:35
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'm trying to register a python callback to be called from my C code using Ctypes. Everything works fine on my computer, but python crashes when the code runs in an ARM device.
In my computer I'm using python 3.6.6 and this ARM device uses python 3.6.3. I'm using buildroot to generate the images.
Well, after some tests seems that the problem is related to CFUNCTYPE.
The following code only test the CFUNCTYPE, and it runs on my computer but crashes (segmentation fault) on the ARM device:
from ctypes import *
def func():
print("func called")
CALLBACK = CFUNCTYPE(None)
callback = CALLBACK(func)
print("Calling callback")
callback()
print("Done!")
The result in my computer is:
Calling callback
func called
Done!
The result in the ARM device is:
Calling callback
Segmentation fault
Is this a bug in CFUNCTYPE? Or I need to do something different? I'm running a lot of python code in this device and everything runs fine, except this CFUNCTYPE.
Thanks
python callback crash ctypes buildroot
asked Nov 21 at 16:37
Dgdiniz
83
I'm trying to register a python callback to be called from my C code using Ctypes. Everything works fine on my computer, but python crashes when the code runs in an ARM device.
In my computer I'm using python 3.6.6 and this ARM device uses python 3.6.3. I'm using buildroot to generate the images.
Well, after some tests seems that the problem is related to CFUNCTYPE.
The following code only test the CFUNCTYPE, and it runs on my computer but crashes (segmentation fault) on the ARM device:
from ctypes import *
def func():
print("func called")
CALLBACK = CFUNCTYPE(None)
callback = CALLBACK(func)
print("Calling callback")
callback()
print("Done!")
The result in my computer is:
Calling callback
func called
Done!
The result in the ARM device is:
Calling callback
Segmentation fault
Is this a bug in CFUNCTYPE? Or I need to do something different? I'm running a lot of python code in this device and everything runs fine, except this CFUNCTYPE.
Thanks
python callback crash ctypes buildroot
python callback crash ctypes buildroot
asked Nov 21 at 16:37
Dgdiniz
83
asked Nov 21 at 16:37
Dgdiniz
83
asked Nov 21 at 16:37
Dgdiniz
83
asked Nov 21 at 16:37
Dgdiniz
83
asked Nov 21 at 16:37
Dgdiniz
83
83
FYI, this works calling the callback on Windows with both 32- and 64-bit Pythons. I normally only call callbacks like this from C but calling from Python works on Intel architecture. Seems like a bug.
– Mark Tolonen
Nov 22 at 2:17
Yes, seems like a bug. I'll also call this from C. This is only a short example to activate the bug. I found an alternative solution using Cython. I created a cython file between my python and C code. This way I can register the callbacks in a similar way.
– Dgdiniz
Nov 23 at 3:35
add a comment |
FYI, this works calling the callback on Windows with both 32- and 64-bit Pythons. I normally only call callbacks like this from C but calling from Python works on Intel architecture. Seems like a bug.
– Mark Tolonen
Nov 22 at 2:17
Yes, seems like a bug. I'll also call this from C. This is only a short example to activate the bug. I found an alternative solution using Cython. I created a cython file between my python and C code. This way I can register the callbacks in a similar way.
– Dgdiniz
Nov 23 at 3:35
FYI, this works calling the callback on Windows with both 32- and 64-bit Pythons. I normally only call callbacks like this from C but calling from Python works on Intel architecture. Seems like a bug.
– Mark Tolonen
Nov 22 at 2:17
FYI, this works calling the callback on Windows with both 32- and 64-bit Pythons. I normally only call callbacks like this from C but calling from Python works on Intel architecture. Seems like a bug.
– Mark Tolonen
Nov 22 at 2:17
Yes, seems like a bug. I'll also call this from C. This is only a short example to activate the bug. I found an alternative solution using Cython. I created a cython file between my python and C code. This way I can register the callbacks in a similar way.
– Dgdiniz
Nov 23 at 3:35
Yes, seems like a bug. I'll also call this from C. This is only a short example to activate the bug. I found an alternative solution using Cython. I created a cython file between my python and C code. This way I can register the callbacks in a similar way.
– Dgdiniz
Nov 23 at 3:35
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53416698%2fpython-ctypes-cfunctype-crashes-in-arm-devices%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
FYI, this works calling the callback on Windows with both 32- and 64-bit Pythons. I normally only call callbacks like this from C but calling from Python works on Intel architecture. Seems like a bug.
– Mark Tolonen
Nov 22 at 2:17
Yes, seems like a bug. I'll also call this from C. This is only a short example to activate the bug. I found an alternative solution using Cython. I created a cython file between my python and C code. This way I can register the callbacks in a similar way.
– Dgdiniz
Nov 23 at 3:35