Errors seen in LOGS/font-manager-0.5.7-4.fc17

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

Raw build logs can be seen here

Reference leaks

Code paths in which the reference count of an object is left too high, leading to memory leaks

src/lib/fm-pyfontutils.c FT_Get_File_Info ob_refcnt of PyStringObject is 1 too high
src/lib/fm-pyfontutils.c FT_Get_File_Info ob_refcnt of '*fileinfo' is 1 too high
src/lib/fm-pyfontutils.c FcFileList ob_refcnt of PyStringObject 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)

src/lib/fm-pyfontutils.c FT_Get_File_Info calling PyDict_SetItem with NULL as argument 2 (D.25555) at src/lib/fm-pyfontutils.c:223
src/lib/fm-pyfontutils.c FT_Get_File_Info calling PyDict_SetItem with NULL as argument 3 (D.25554) at src/lib/fm-pyfontutils.c:223
src/lib/fm-pyfontutils.c FT_Get_File_Info calling PyDict_SetItem with NULL as argument 2 (D.25552) at src/lib/fm-pyfontutils.c:222
src/lib/fm-pyfontutils.c FT_Get_File_Info calling PyDict_SetItem with NULL as argument 3 (D.25551) at src/lib/fm-pyfontutils.c:222
src/lib/fm-pyfontutils.c FcFileList calling PyList_Append with NULL as argument 1 (fontlist) at src/lib/fm-pyfontutils.c:143

Implementation notes for gcc-with-cpychecker

The following "Py" functions were used but aren't yet explicitly handled by gcc-with-cpychecker