Thank you Mark! Coverity should not become a substitute for competent design and careful coding. There have been a lot of false positives so they should be marked as such. The same thing goes for compiler warnings. They are just that, a warning that you may have done something you did not intend. If you did intend your code to work that way, it is just noise and should be recognized as such.
On 4/13/2015 6:32 PM, Mark Roszko 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. > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
