Imperial College London

ProfessorAlastairDonaldson

Faculty of EngineeringDepartment of Computing

Professor of Programming Languages
 
 
 
//

Contact

 

+44 (0)20 7594 8266alastair.donaldson Website

 
 
//

Location

 

422Huxley BuildingSouth Kensington Campus

//

Summary

 

Publications

Citation

BibTex format

@inproceedings{Cadar:2016:10.1145/2889160.2889206,
author = {Cadar, C and Donaldson, A},
doi = {10.1145/2889160.2889206},
publisher = {ACM},
title = {Analysing the Program Analyser},
url = {http://dx.doi.org/10.1145/2889160.2889206},
year = {2016}
}

RIS format (EndNote, RefMan)

TY  - CPAPER
AB - It is the year 2025. FutureCorp, the privatesector defence contractor to whom the US government hasoutsourced its management of nuclear weapons, has justhad its missile control software hijacked by terrorists. Itis only a matter of hours before Armageddon. The CEOof FutureCorp, Dr F. Methods, is incredulous: “This isimpossible”, he told one of our reporters. “We used programanalysis to formally prove that the software was secure!”.“Ah, Dr Methods,” responded open-source developer Mr B.Door, “But did you check the analyser?”
AU - Cadar,C
AU - Donaldson,A
DO - 10.1145/2889160.2889206
PB - ACM
PY - 2016///
TI - Analysing the Program Analyser
UR - http://dx.doi.org/10.1145/2889160.2889206
UR - http://hdl.handle.net/10044/1/29767
ER -