d470abe976
Many ABIs impose some kind of alignment constraints on the stack pointer. For example, both the AArch32 and x86_64 SysV ABIs specify that the end of the spilled argument list is aligned to 2*w where w is the number of bytes in a word. Since macaw-symbolic has no notion of the ABI in use, its ABI-agnostic code could only ever satisfy such alignment constraints accidentally. Clients wishing to spill arguments to the stack should do so with ABI-specific functionality. |
||
|---|---|---|
| .. | ||
| examples | ||
| src/Data/Macaw | ||
| test | ||
| .hlint.yaml | ||
| ChangeLog.md | ||
| LICENSE | ||
| macaw-symbolic.cabal | ||
| README.org | ||
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.