On Fri, 2020-08-07 at 08:17 +0200, Stephan Bergmann wrote:
The above CIDs 1462308--1462314, 1462316, and 1462318 all appear to
center on the false assumption that TYPELIB_DANGER_GET
(include/typelib/typedescription.h) could destroy its
*ppMacroTypeDescr argument (while it will actually only shave off an
excess refcount via typelib_typedescription_release).
Question is whether there is a good way to centrally teach Coverity
Scan about its false assumption there.
It's probable that we had all these before and marked them manually in
the coverity UI as false positive but loplugin:flatten (or somethine
like that) changed the code enough that coverity doesn't recognize it
as the same code anymore and warns about them again.
I don't know a good way to inline mark these up to avoid the warning,
but they are manually set as ignored again and so shouldn't appear in
the next run.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.