kicad-developers team mailing list archive

[Mário Luzeiro <mrluzeiro@xxxxx>]

Thanks Mark it works.

I think a quick summary of the main occurrences can be extracted:

High impact:
Resource leaks
Memory - corruptions
Memory - illegal accesses
Uninitialized variables

Medium impact:
Uninitialized members
Control flow issues
Null pointer dereferences
Incorrect expression
Integer handling issues
Error handling issues
Insecure data handling

It gives an idea of the usually mistakes.

Regards,
Mario Luzeiro

________________________________________
From: Mark Roszko [mark.roszko@xxxxxxxxx]
Sent: 14 April 2015 04:58
To: Mário Luzeiro
Cc: Cirilo Bernardo; KiCad Developers
Subject: Re: [Kicad-developers] [PATCH] S3D Mesh Smart Pointer

I'll add that you can request access to at least view the kicad
Defects it finds here:
https://scan.coverity.com/projects/3606?tab=overview


On Mon, Apr 13, 2015 at 6:49 PM, Mario Luzeiro <mrluzeiro@xxxxx> wrote:
> Hi Mark,
> yeah , you are right, that one maybe was a very specific situation. I was thinking something more easy and general like "you should initialize your vars".
>
> In that case where can we have a look in  the Coverity documentation?
>
> Is that something I can run / test  myself?
>
> Regards,
> Mario Luzeiro On 14 Apr 2015 00:32, Mark Roszko <mark.roszko@xxxxxxxxx> wrote:
>>
>> >So perhaps some one can summarize this changes need
>>
>> There's hundreds of ways and "reasons" why Coverity could have thrown
>> the "use after free" error that Brian is fixing. There is no one size
>> fits all solution.



--
Mark