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.
Code paths in which the reference count of an object is left too high, leading to memory leaks
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
pyewf.c | pyewf_open | returning (PyObject*)NULL without setting an exception |
The following "Py" functions were used but aren't yet explicitly handled by gcc-with-cpychecker
PySequence_Check