This is a summary of errors seen when compiling with an experimental static analysis tool
Raw build logs can be seen here
Code paths in which the reference count of an object is left too low. This could lead to the object being deallocated too early, triggering segfaults when later accessed. Over repeated calls, these errors could accumulate, increasing the likelihood of a segfault.
src/python_module.c | pm_load_script | ob_refcnt of return value is 1 too low |
Code paths in which the reference count of an object is left too high, leading to memory leaks
Code paths in which the reference count of an object might too large - but in which the reference in question came from a function not known to the analyzer.
The analyzer assumes such references are new references, but if the function returns a borrowed reference instead, it's probably not a bug
src/python_module.c | get_info | ob_refcnt of '*osync_module' is 1 too high |
These messages are often false-positives: the analysis tool has no knowledge about internal API calls that can lead to an exception being set
The following "Py" functions were used but aren't yet explicitly handled by gcc-with-cpychecker
PyErr_Clear
PyEval_AcquireThread
Py_NewInterpreter