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
Python 2.7 crashes in Linux environment #74663
Comments
Hi all, I have a python script to run as a Weather Station application. The python script runs on Raspberry Pi 3 board. It gets weather data from OpenWeatherMap website and sends result to a remote touch-screen device via COM port to display It uses two main libraries to handle the task: I got the python script just exits without any error after sometimes. Checking the return code with the command "echo $?" in Pi's console window and got 139 which means a Segmentation Fault We tried to generate coredump system when the python script crashes and we got this: I tried to update to Python 2.7.13 but the crashes still happens. My question is if the segmentation fault related to complexobject.c has been reported and fixed? Best regards, |
Hi Huyk, which version of Python does the error message generated? Also, could you try to provide a minimum reproduce python script and upload it? it will be more easy to debug this problem if we can reproduce this. |
Hi Louie Lu, You will need a touch-screen device running corresponding firmware in order to run the python application. FYI, I tried to run only weather data fetching or only COM port communication but the crash did not happen. It happens when I run both tasks. Thanks, |
Hi HuyK, thanks for the issue report, and in particular the pointers to the key external libraries the script uses. It seems ftd2xx relies on ctypes to wrap an external library, which means that this report falls under the general policy of "triggering a segfault with ctypes is assumed to be a bug in the usage of ctypes, rather than a bug in ctypes itself". If you'd like to investigate further before filing a bug report with the ftd2xx authors, you may want to try out the Python 2.7 backport of Python 3's faulthandler library: https://faulthandler.readthedocs.io/ That should be able to give you a Python traceback at the point where the segfault occurs, rather than trying to reverse engineer that information from the core dump. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: