Summary: | Segfault in unit tests | ||
---|---|---|---|
Product: | libsigrokdecode | Reporter: | marian.buschsieweke |
Component: | Build system | Assignee: | Nobody <nobody> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | uwe |
Priority: | Normal | ||
Version: | 0.5.1 | ||
Target Milestone: | --- | ||
Hardware: | x86 | ||
OS: | Linux |
Description
marian.buschsieweke
2018-06-19 16:48:23 CEST
Hm, I'm assuming this is something specific to the Python version or the distro. While I can reproduce it on a quick VM test-image of Alpine Linux, it's not reproducible on various other distros. Can you please try some other box / distro and see if it happens for you regardless of distro? It *might* be a Python bug as well. One working box (Debian unstable x86_64) has 3.6.6r1, my Alpine Linux test-image has 3.6.3, changelog is here: https://docs.python.org/3/whatsnew/changelog.html The 3.6.4 changes include some low-level fixes and crashes in Python itself, maybe it's one of those. Potential candidates are e.g. bpo-20891: Fix PyGILState_Ensure(). When PyGILState_Ensure() is called in a non-Python thread before PyEval_InitThreads(), only call PyEval_InitThreads() after calling PyThreadState_New() to fix a crash. bpo-31532: Fix memory corruption due to allocator mix in getpath.c between Py_GetPath() and Py_SetPath() If you can easily try another Python version, please do and report if that fixes the issue or not. Thanks! Hi, thanks for the fast feedback. Actually, I'm using the edge version of Alpine Linux which includes Python 3.6.4 already. So the specific python bug you mentioned should not be the problem. I'll check with 3.6.5 and an older python version if the segfault persists. Kind regards, Marian Hi, now that Alpine Linux is using python 3.7 sigrok works fine. Therefore, as Uwe Hermann suggested, this seems to be a python bug and not a sigrok bug. In any case it is now resolved for Alpine :-) Kind regards, Marian |