Great. Thanks for keeping this up. If you manage the Coverity instance I'd like to support your effort by closing the loop on whittling down the Coverity issues. Is there a formal path for tracking what Coverity complains about: what's a false positive, what's a real problem, and when things get fixed? How do you want to work that?
We've had some Coverity encounters before but never really followed up with a plan. http://apache-qpid-developers.2158895.n2.nabble.com/static-analysis-td5701419.html -Chuck ----- Original Message ----- > From: "Steve Huston" <[email protected]> > To: [email protected] > Sent: Thursday, June 13, 2013 8:59:24 PM > Subject: C++ code in coverity static analysis > > Hi folks, > > A while back I registered Qpid-C++ for Coverity static analysis, but > didn't really keep it going. I am getting that going again and you may see > some email from coverity to that effect. I'll get it submitted regularly > and try to knock down the false positives that are obvious before asking > more people to look at it. > > FYI. > > -Steve > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
