Errors seen in LOGS/yum-metadata-parser-1.1.4-6.fc17

This is a summary of errors seen when compiling with an experimental static analysis tool

Raw build logs can be seen here

Reference leak within initialization

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

sqlitecache.c init_sqlitecache ob_refcnt of PyIntObject is 1 too high

Segfaults within error-handling paths

Code paths in error-handling that will lead to a segmentatation fault (e.g. under low memory conditions)

sqlitecache.c progress_cb dereferencing NULL (MEM[(struct PyTupleObject *)args].ob_item) at sqlitecache.c:351

Returning (PyObject*)NULL without setting an exception

These messages are often false-positives: the analysis tool has no knowledge about internal API calls that can lead to an exception being set
sqlitecache.c py_update returning (PyObject*)NULL without setting an exception