Static code analysis - the easiest way to improve

[Aleix Pol]

On Sun, Feb 28, 2016 at 3:59 PM, Jaroslaw Staniek <staniek at kde.org> wrote:
> Hi,
> Just to remind. If someone has some time to fix bugs, KDE
> apps/Calligra/Frameworks static analysis is the easiest way to improve
> Calligra.
> Code defects are well explained (like uninitialized variables or
> NULL-related failures). Much easier than actually reading that bug reports,
> analysing them and testing.
>
> So please, these are low-hanging fruits. Hundreds of them.
>
> Visit:
> https://scan.coverity.com/projects/kde
> You can request access if you don't have it yet.
>
> Let us know in this thread if code you're interested in isn't there.

To be honest, I've tried to use it many times, but I always seem to
end up diving in warnings in other projects. It's hard to filter for
projects I have a grasp on.

How do you deal with this?

Regards,
Aleix