Directed Proof Generation for Machine Code

dc.contributor.authorThakur, A.en_US
dc.contributor.authorLim, J.en_US
dc.contributor.authorLal, A.en_US
dc.contributor.authorBurton, A.en_US
dc.contributor.authorDriscoll, E.en_US
dc.contributor.authorElder, M.en_US
dc.contributor.authorAndersen, T.en_US
dc.contributor.authorReps, T.en_US
dc.date.accessioned2012-03-15T17:24:44Z
dc.date.available2012-03-15T17:24:44Z
dc.date.created2010en_US
dc.date.issued2010en_US
dc.description.abstractWe 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.mimetypeapplication/pdfen_US
dc.identifier.citationTR1669en_US
dc.identifier.urihttp://digital.library.wisc.edu/1793/60698
dc.publisherUniversity of Wisconsin-Madison Department of Computer Sciencesen_US
dc.titleDirected Proof Generation for Machine Codeen_US
dc.typeTechnical Reporten_US

Files

Original bundle

Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
TR1669.pdf
Size:
462.77 KB
Format:
Adobe Portable Document Format