On 12/05/2016 05:31 PM, Andrew Johnson wrote:
> Does anyone have recent experience with static code analysis tools?
> There are examples and links under the "show details" area for this
> section of the Best Practices page. I could use some help here.
I made some use of cppcheck with a project this past spring. It's easy
to run, packaged by debian (thus available on travis-ci.org), and FOSS.
The downsides are those common to static analysis. It's chatty.
That said. I just ran it on src/libCom/ and quickly parsed through the
output. cppcheck finds an potential memory leak in macEnv.c.
> [src/libCom/macLib/macEnv.c:66]: (error) Common realloc mistake: 'dest' nulled but not freed upon failure
> dest = realloc(dest, n);
Sorting through this for all of Base will take some time.
http://cppcheck.sourceforge.net/
- Replies:
- Re: CII Best Practices Badge Status Andrew Johnson
- References:
- CII Best Practices Badge Status Andrew Johnson
- Navigate by Date:
- Prev:
CII Best Practices Badge Status Andrew Johnson
- Next:
Re: CII Best Practices Badge Status Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
- Navigate by Thread:
- Prev:
CII Best Practices Badge Status Andrew Johnson
- Next:
Re: CII Best Practices Badge Status Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
|