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 error-handling that will lead to a segmentatation fault (e.g. under low memory conditions)
These messages are often false-positives: the analysis tool has no knowledge about internal API calls that can lead to an exception being set
jinja/_speedups.c | BaseContext_push | returning (PyObject*)NULL without setting an exception |
The following "Py" functions were used but aren't yet explicitly handled by gcc-with-cpychecker
PyList_Reverse
PyMapping_HasKey
PyObject_IsInstance