Serviceeinschränkungen vom 12.-22.02.2026 - weitere Infos auf der UB-Homepage
  • A type system for format strin...

Treffer: A type system for format strings

Title:
A type system for format strings
Authors:
Konstantin Weitz, Gene Kim, Siwakorn Srisakaokul, Michael D. Ernst
Contributors:
The Pennsylvania State University CiteSeerX Archives
Source:
http://homes.cs.washington.edu/~mernst/pubs/format-string-issta2014.pdf.
Publication Year:
2014
Collection:
CiteSeerX
Subject Terms:
Categories and Subject Descriptors D.2.4 [Software Engineering, Software/Program Verification— Reliability, D.3.3 [Programming Languages, Language Con- structs and Features—Data types and structures General Terms Experimentation, Languages, Reliability, Verification Keywords Format string
Document Type:
Fachzeitschrift text
File Description:
application/pdf
Language:
English
Relation:
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.645.7261
Availability:
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.645.7261
http://homes.cs.washington.edu/~mernst/pubs/format-string-issta2014.pdf
Rights:
Metadata may be used without restrictions as long as the oai identifier remains attached to it.
Accession Number:
edsbas.72A72F06
Database:
BASE

Weitere Informationen

Most programming languages support format strings, but their use is error-prone. Using the wrong format string syntax, or passing the wrong number or type of arguments, leads to unintelligible text output, program crashes, or security vulnerabilities. This paper presents a type system that guarantees that calls to format string APIs will never fail. In Java, this means that the API will not throw exceptions. In C, this means that the API will not return negative values, corrupt memory, etc. We instantiated this type system for Java’s Formatter API, and evaluated it on 6 large and well-maintained open-source projects. Format string bugs are common in practice (our type system found 104 bugs), and the annotation burden on the user of our type system is low (on average, for every bug found, only 1.0 annotations need to be written).