Directed Proof Generation for Machine Code
| dc.contributor.author | Thakur, A. | en_US |
| dc.contributor.author | Lim, J. | en_US |
| dc.contributor.author | Lal, A. | en_US |
| dc.contributor.author | Burton, A. | en_US |
| dc.contributor.author | Driscoll, E. | en_US |
| dc.contributor.author | Elder, M. | en_US |
| dc.contributor.author | Andersen, T. | en_US |
| dc.contributor.author | Reps, T. | en_US |
| dc.date.accessioned | 2012-03-15T17:24:44Z | |
| dc.date.available | 2012-03-15T17:24:44Z | |
| dc.date.created | 2010 | en_US |
| dc.date.issued | 2010 | en_US |
| dc.description.abstract | We present the algorithms used in McVeto (Machine-Code VErification TOol), a tool to check whether a stripped machine-code program satisfies a safety property. The verification problem that McVeto addresses is challenging because it cannot assume that it has access to (i) certain structures commonly relied on by source-code verification tools, such as control-flow graphs and call-graphs, and (ii) meta-data, such as information about variables, types, and aliasing. It cannot even rely on out-of-scope local variables and return addresses being protected from the program's actions. What distinguishes McVeto from other work on software model checking is that it shows how verification of machine-code can be performed, while avoiding conventional techniques that would be unsound if applied at the machine-code level. | en_US |
| dc.format.mimetype | application/pdf | en_US |
| dc.identifier.citation | TR1669 | en_US |
| dc.identifier.uri | http://digital.library.wisc.edu/1793/60698 | |
| dc.publisher | University of Wisconsin-Madison Department of Computer Sciences | en_US |
| dc.title | Directed Proof Generation for Machine Code | en_US |
| dc.type | Technical Report | en_US |
Files
Original bundle
1 - 1 of 1