Analysing the program analyser
Author(s) -
Cristian Cadar,
Alastair F. Donaldson
Publication year - 2016
Publication title -
spiral (imperial college london)
Language(s) - English
Resource type - Conference proceedings
DOI - 10.1145/2889160.2889206
Subject(s) - computer science , correctness , analyser , program analysis , software quality , compiler , reliability (semiconductor) , software engineering , set (abstract data type) , quality (philosophy) , regression testing , software , programming language , reliability engineering , software system , software development , software construction , engineering , physics , power (physics) , chemistry , philosophy , chromatography , quantum mechanics , epistemology
It is the year 2025. FutureCorp, the private sector defence contractor to whom the US government has outsourced its management of nuclear weapons, has just had its missile control software hijacked by terrorists. It is only a matter of hours before Armageddon. The CEO of FutureCorp, Dr F. Methods, is incredulous: “This is impossible”, he told one of our reporters. “We used program analysis to formally prove that the software was secure!”. “Ah, Dr Methods,” responded open-source developer Mr B. Door, “But did you check the analyser?
Accelerating Research
Robert Robinson Avenue,
Oxford Science Park, Oxford
OX4 4GP, United Kingdom
Address
John Eccles HouseRobert Robinson Avenue,
Oxford Science Park, Oxford
OX4 4GP, United Kingdom