macaw/symbolic
Daniel Matichuk cd5dfe8c65
macaw-symbolic: record original block endings when making a CFG slice (#185)
* reify block exit in macaw extension

* add return address to block end classification

* use global variable to retain block endings

* update to mkBlockSliceCFG signature

* add haddocks for MacawBlockEnd

Co-authored-by: Tristan Ravitch <tristan@galois.com>
2021-01-11 16:56:54 -08:00
..
examples symbolic: Clean up the memory mapping API 2019-01-11 13:21:04 -08:00
src/Data/Macaw macaw-symbolic: record original block endings when making a CFG slice (#185) 2021-01-11 16:56:54 -08:00
test This commit re-implements the memory model used by macaw symbolic 2020-02-11 09:58:53 -08:00
LICENSE Update license information. 2017-09-27 15:59:06 -07:00
macaw-symbolic.cabal Switch from ansi-wl-pprint to the prettyprinter package. 2020-12-02 11:38:19 -08:00
README.org Clean up and document the macaw-symbolic API 2019-01-10 18:20:54 -08:00

Overview

The macaw-symbolic library provides a mechanism for translating machine code functions discovered by macaw into Crucible CFGs that can then be symbolically simulated.

The core macaw-symbolic library supports translating generic macaw into crucible, but is not a standalone library. To translate actual machine code, an architecture-specific backend is required. For example, macaw-x86-symbolic can be used to translate x86_64 binaries into crucible. Examples for using macaw-symbolic (and architecture-specific backends) are available in Data.Macaw.Symbolic.

In order to avoid API bloat, the definitions required to implement a new architecture-specific backend are exported through the Data.Macaw.Symbolic.Backend module.

An additional module, Data.Macaw.Symbolic.Memory, provides an example of how to handle memory address translation in the simulator for machine code programs. There are other possible ways to translate memory addresses, but this module provides a versatile example that can serve many common use cases.