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
nautilus-python-object.c | nautilus_python_object_cancel_update | ob_refcnt of new ref from call to PyObject_CallMethod is 1 too high |
Code paths in error-handling that will lead to a segmentatation fault (e.g. under low memory conditions)
nautilus-python-object.c | nautilus_python_boxed_new | dereferencing NULL (self->gtype) at nautilus-python-object.c:133 |
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
The following "Py" functions were used but aren't yet explicitly handled by gcc-with-cpychecker
PyErr_Fetch
PyImport_ImportModuleLevel
PyList_Insert
PyObject_IsSubclass
PySequence_Check
Py_IsInitialized