This is a summary of errors seen when compiling with an experimental static analysis tool
Raw build logs can be seen here
Code paths that will lead to a segmentatation fault
krb5module.c | Principal_getitem | dereferencing NULL (d->length) at krb5module.c:2430 |
Code paths in which the reference count of an object is left too high, leading to memory leaks
Code paths in error-handling that will lead to a segmentatation fault (e.g. under low memory conditions)
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
These messages are often false-positives: the analysis tool has no knowledge about internal API calls that can lead to an exception being set