Errors seen in LOGS/python-libasyncns-0.7.1-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 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.

Reference leaks

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

Segfaults within error-handling paths

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

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

addrinfoquery.c

AddrInfoQuery_get_done

returning (PyObject*)NULL without setting an exception