Report from llvms static analysis tool

Caolán McNamara caolanm at
Mon Oct 5 06:56:31 PDT 2015

On Mon, 2015-10-05 at 10:29 +0200, Stephan Bergmann wrote:
> your rather short list of 1385 issues looks more
> promising now

The majority of those "Called C++ object pointer is null" are the
examples of archaic DBG_ASSERT and OSL_ENSURE, etc macros which could
be converted into "assert" because they test for null pointers and the
non-debug code goes on to unconditionally deference them.

e.g. all the basctl warnings are that

So if were to clear the scan-build warnings on that topic, mostly by
converting to assert, then when the dust settles we could perhaps mass
convert the remaining DBG_ASSERTs to SAL_WARN


More information about the LibreOffice mailing list