[Bf-committers] PVS-Studio Static Analysis

[Nicholas Bishop]

Not necessarily; different static analyzers can detect different types
of potential problems. The PVS analysis contains some interesting
things like the "Misprint in a homogeneous code block" section that I
don't think clang's analyzer does.

On Tue, Apr 24, 2012 at 7:20 PM, Tom M <letterrip at gmail.com> wrote:
> We have a page with generated CLang static analysis,
>
> http://clang.blenderheads.org/trunk/
>
> It probably shows the same bugs as PVS-Studio does.
>
> LetterRip
>
> On Tue, Apr 24, 2012 at 4:15 PM, Nicholas Bishop
> <nicholasbishop at gmail.com> wrote:
>> I think some of these have been fixed already in recent commits from Campbell.
>>
>> On Tue, Apr 24, 2012 at 7:11 PM, Jason Wilkins
>> <jason.a.wilkins at gmail.com> wrote:
>>> http://www.viva64.com/en/b/0145/#ID0EO3BK
>>>
>>> It appears that Andrey Karpov has done an analysis of Blender source
>>> code using his PVS-Studio tool.  He did this just yesterday, so I
>>> assume the problems he found are still in the source.  He offers free
>>> licenses to open source project members (3500 euro software otherwise,
>>> wow).
>>>
>>> I was thinking of investigating the problems he found and seeing if I
>>> could fix them.
>>> _______________________________________________
>>> Bf-committers mailing list
>>> Bf-committers at blender.org
>>> http://lists.blender.org/mailman/listinfo/bf-committers
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers