Nick Coghlan added the comment: 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. ---------- nosy: +ncoghlan resolution: -> third party stage: -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30478> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
