Checking System Rules Using System-Specific, Programmer-Written Compiler Extensions

Evaluating the relation between coding standard violations and faultswithin and across software versions

“…We start gathering this information by checking which file versions are associated with faults present in the issue database (5). We proceed to compute a difference with previous revisions, indicating which changes were made in order to solve the issue, and marking the modified lines.…”

“…Over the years various tools have become available that automate the checking of rules in a standard, helping developers locate potentially difficult or problematic areas in the code. These include commercial offerings (e.g., QA-C, 1 K7, 2 CodeSonar 3 ) as well as academic solutions (e.g., [12,5,7]). Such tools generally come with their own sets of rules, but can often be adapted so also custom standards can be checked automatically.…”

Behavioural Analysis of an I2C Linux Driver

“…Probably the best known in that direction is the work of Engler et al(e.g. [13]). In [19], which introduces the static analysis tool UNO, case studies of verification of Linux device drivers with the tool are mentioned, although no details of the results are presented.…”

Toasters, Seat Belts, and Inferring Program Properties

“…We do, however, have many of the essential technologies in place to provide meaningful guarantees regarding software systems. Research tools have been developed to check properties of large programs [5,10,12,14,20,22], and dozens of companies are now offering analysis tools and services (e.g., Coverity, Fortify, Ounce Labs, PolySpace, Reflective).…”