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 high, leading to memory leaks
Code paths in which the reference count of an object is left too high, but within an initialization routine, and thus likely to only happen once
snackmodule.c | init_snack | ob_refcnt of PyIntObject is 1 too high |
snackmodule.c | init_snack | ob_refcnt of PyStringObject is 1 too high |
Code paths in error-handling that will lead to a segmentatation fault (e.g. under low memory conditions)
These messages are often false-positives: the analysis tool has no knowledge about internal API calls that can lead to an exception being set
snackmodule.c | widgetCheckboxTreeGetEntryValue | returning (PyObject*)NULL without setting an exception |
The following "Py" functions were used but aren't yet explicitly handled by gcc-with-cpychecker
PyErr_Clear
PyObject_Free
PyObject_Malloc
Py_FindMethod