Hi Steve,
/qpidbuilds/trunk/qpid/cpp/src/qmf/engine/ValueImpl.cpp line 287-288: CID 401186 (#11 of 11): Resource leak (RESOURCE_LEAK)26. leaked_storage: Variable "subval" going out of scope leaks the storage it points to. I can take a look at this. ----- Original Message ----- > From: "Steve Huston" <[email protected]> > To: [email protected] > Sent: Monday, June 17, 2013 11:06:46 PM > Subject: Re: C++ code in coverity static analysis > > Thanks Chuck. Getting a plan to address these would be great. > > For now, could someone please check out: > > /qpidbuilds/trunk/qpid/cpp/src/qmf/engine/ValueImpl.cpp line 287-288: > > CID 401186 (#11 of 11): Resource leak (RESOURCE_LEAK)26. leaked_storage: > Variable "subval" going out of scope leaks the storage it points to. > > > It's possible to use the web page to mark things should be ignored. I'll > try to find some sensible way to divide the current set of untriaged > issues. > > -Steve > > On 6/14/13 8:51 AM, "Chuck Rolke" <[email protected]> wrote: > > >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-td5701 > >419.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] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- -K --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
