Skip to content
This repository has been archived by the owner on Mar 30, 2021. It is now read-only.

VIM XTU Analysis

Whisperity edited this page Jan 26, 2017 · 9 revisions

Baseline:

VIM without xtu - clang 4.0 http://md-mtas2.tsp.eth.ericsson.se:4999/#run=7

VIM XTU with XTU - clang 4.0

http://md-mtas2.tsp.eth.ericsson.se:4999/#run=8

###Summary

Analyzed project All Non-CTU Findings (baseline) All CTU Findings New CTU findings Disappeared findings Successfully analyzed Failed to analyze Analysis Time (baseline)[s] Analysis Time XTU (1st Phase + 2nd Phase)[s] Median of bug path length (BPL) in baseline Median of BPL CTU Median of BPL of new findings Median of BPL of disappeared findings
vim 52 96 57 17 50 files 12 files 89.13 162.55 9 11 17 15
Checker ID Number of new findings
NOT FOUND 2
core.CallAndMessage 2
core.NonNullParamChecker 8
core.NullDereference 15
core.UndefinedBinaryOperatorResult 4
core.uninitialized.Assign 1
core.uninitialized.Branch 1
unix.Malloc 7

Most important true positives found with XTU

  1. core.NullDereference http://md-mtas2.tsp.eth.ericsson.se:4999/#baseline=7&newcheck=8&report=1049

False positives

  1. http://md-mtas2.tsp.eth.ericsson.se:4999/#baseline=7&newcheck=8&report=1046 (actually the conclusion is correct, but does not consider that there is such a programming convention in c)