[Freeswitch-dev] Static code annalysis with Klocwork
mike at jerris.com
Sat Nov 8 09:41:07 PST 2008
It helped quite a bit, many of the identified problems were fixed in
tree and a review of the svn logs will find all the issues identified
in the commit notes. I would guess there were hundreds of issues
found. We never got them to run another test run on more recent code
(we requested about 6 months ago and they never did it). We do use
other static code analysis tools as well including those built in to
MSVC Team Edition on a fairly regular ongoing basis but those require
a lot more up front work marking function parameters in the code.
While there is some cost in doing that, I have found that you get
better results both in many more real errors found and many less false
issues found. We are more than interested in continuing this work if
klockwork ever responds back, or more likely enhancing our code
coverage with the msvc code analysis tagging and we are looking for
those with access to that software who have time and would like to
On Nov 8, 2008, at 11:47 AM, Simon Shaw wrote:
> Did this help you?
> How many bugs did you find?
> Are the results available to the general public?
> From: freeswitch-dev-bounces at lists.freeswitch.org [mailto:freeswitch-dev-bounces at lists.freeswitch.org
> ] On Behalf Of Brian West
> Sent: Thursday, November 06, 2008 8:07 PM
> To: freeswitch-dev at lists.freeswitch.org
> Subject: Re: [Freeswitch-dev] Static code annalysis with Klocwork
> Its already been done once. ;)
> On Nov 6, 2008, at 12:04 PM, Simon Shaw wrote:
> Anybody tried running Freeswitch through the Klocwork C++ static
> analysis tool?
> Freeswitch-dev mailing list
> Freeswitch-dev at lists.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Freeswitch-dev