This is a summary of errors seen when compiling with an experimental static analysis tool
Raw build logs can be seen here
Code paths in which the reference count of an object is left too high, leading to memory leaks
OpenSSL/crypto/crypto.c | global_passphrase_callback | ob_refcnt of '*ret' is 1 too high |
Code paths in which the reference count of an object is too low, but within an initialization routine, and thus likely to only happen once
OpenSSL/crypto/crypto.c | initcrypto | ob_refcnt of '*crypto_Error.0' is 1 too low |
Code paths in error-handling that will lead to a segmentatation fault (e.g. under low memory conditions)
OpenSSL/crypto/crypto.c | global_passphrase_callback | dereferencing NULL (argv->ob_refcnt) at OpenSSL/crypto/crypto.c:49 |
These messages are often false-positives: the analysis tool has no knowledge about internal API calls that can lead to an exception being set
The following "Py" functions were used but aren't yet explicitly handled by gcc-with-cpychecker
PyThread_allocate_lock
PyThread_release_lock