A moment ago I wrote: > > I've downloaded a .csv summary of the 350+ bugs Coverity* identified > in some version of 2.5 as it stood in February, brought the .csv file > into OpenOffice, deleted a number of columns that have no meaning for > us since we haven't set up the project management scheme they reflect, > and sorted the resulting table on the fully qualified source file > name. Give a few minutes to get these files up to a public server and > I'll tell you where it is. >
See http://www.mediafire.com/?9dduyf18c926x coverity-exported.csv is the original file. coverity-exported-edited.ods is the file I created in OpenOffice. and it's 353 bugs. > This can be compared to the 56 bugs reported by Clang on the current > v2.5_branch (sorry, things are a bit out of sync because of the time > displacement, but it will be instructive anyway). > > The Clang bugs can be seen referenced to the actual offending lines in > the source code on the buildbot site. > > A Coverity/Scan account will be needed to see the Coverity-identified > bugs referenced to the actual offending lines in the source code. Make > sure you have an extra large cup of coffee at hand before you start. > > Regards, > Kent > > *They seem to be calling this online site the Coverity Integrity > Manager now, although it has a scan5.coverity.com URL, and make > reference to the "Coverity Analysis Tools". Maybe I'm just confused by > the nomenclature. > > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
