Errors seen in LOGS/clearsilver-0.10.5-17.fc17

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

Raw build logs can be seen here

Reference count too low

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.

neo_cgi.c p_cgi_set_upload_cb ob_refcnt of '*p_cgi' is 1 too low

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

neo_cgi.c p_cgiwrap_init ob_refcnt of '*sys' is 1 too high
neo_cgi.c p_cgiwrap_init ob_refcnt of '*os' is 1 too high
neo_cgi.c p_cgiwrap_init ob_refcnt of '*p_stdin' is 1 too high
neo_cgi.c p_cgiwrap_init ob_refcnt of '*p_stdout' is 1 too high
neo_cgi.c p_cgiwrap_init ob_refcnt of '*p_env' 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)

neo_cgi.c python_upload_cb dereferencing NULL (result->ob_refcnt) at neo_cgi.c:146

Possible reference leaks

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

neo_cgi.c p_cgiwrap_init ob_refcnt of new ref from (unknown) cgiwrap is 1 too high