Static Analysis: results of FUDcon Lawrence hackfest

Kamil Dudka kdudka at redhat.com
Fri Jan 25 15:46:22 UTC 2013


On Friday 25 January 2013 16:01:15 Jerry James wrote:
> On Fri, Jan 25, 2013 at 5:16 AM, Kamil Dudka <kdudka at redhat.com> wrote:
> > On Thursday, January 24, 2013 14:11:11 Jerry James wrote:
> >> It is not, but see http://jjames.fedorapeople.org/blast/ for an
> >> experimental RPM.  If we could get the Vampyre developers to remove
> >> "for research purposes only" from their license, we could get both
> >> Vampyre and BLAST into Fedora.
> >>
> >> Note that we also have why and why3 in Fedora, by the way.
> >
> > The above tools are not bug finding tools.  They will not give you a list
> > of bugs detected in the input program.  You need to specify a property to
> > verify and the tools then return a yes/no answer, supported by a (usually
> > hard to read) counter-example.  Such tools are not intended for a fully
> > automatic static analysis.
> >
> > Kamil
> 
> David mentioned Frama-C, so I thought he would be interested in these
> tools, too.

I see Frama-C as a tool somewhere in the middle.  It is a framework you can 
use to build static analysis tools on.  On the other hand, it comes also with 
a set of checkers that work out of the box and can be used to find bugs.

Kamil


More information about the devel mailing list