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

VIM XTU Analysis

Daniel Krupp edited this page Mar 24, 2017 · 9 revisions

Baseline:

VIM without xtu - clang 4.0 http://cc.inf.elte.hu:8080/#run=193

VIM XTU with XTU - clang 4.0

http://cc.inf.elte.hu:8080/#run=194

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 78 160 97 23 61 files 1 files 145.7 466 + 6 9.5 15 17 15

New findings

------------------- Bugs grouped by checker ------------------
------------------------------------------
Checker ID                         | Count
------------------------------------------
NOT FOUND                          | 15   
core.CallAndMessage                | 7    
core.NonNullParamChecker           | 18   
core.NullDereference               | 31   
core.UndefinedBinaryOperatorResult | 7    
core.uninitialized.Assign          | 3    
core.uninitialized.Branch          | 6    
unix.Malloc                        | 10   
------------------------------------------


------------------- Metrics ------------------
Total # of bugs:             97
MIN BugPath length:          3
MAX BugPath length:          93
Mean length:                 23.9484536082

 %:      25% percentile: 14.0
 %:      50% percentile: 21.0
 %:      75% percentile: 32.0
 %:      90% percentile: 41.0

Most important true positives found with XTU

  1. core.NullDereference http://cc.inf.elte.hu:8080/#baseline=193&newcheck=194&report=19859

False positives

  1. http://cc.inf.elte.hu:8080/#baseline=193&newcheck=194&report=19824 (actually the conclusion is correct, but does not consider that there is such a programming convention in c)