Errors seen in LOGS/pyrit-0.4.0-5.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

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

cpyrit/_cpyrit_cpu.c	EAPOLCracker_solve	returning (PyObject*)NULL without setting an exception
cpyrit/_cpyrit_cpu.c	PcapDevice_open_live	returning (PyObject*)NULL without setting an exception
cpyrit/_cpyrit_cpu.c	PcapDevice_open_offline	returning (PyObject*)NULL without setting an exception
cpyrit/_cpyrit_cpu.c	PcapDevice_send	returning (PyObject*)NULL without setting an exception