This is the main repository for the Macaw binary analysis framework with two key goals: binary code discovery and symbolic execution of machine code. This framework is implemented to offer extensible support for architectures (i.e., library clients can add their own architectures and opt in to the architecture support they need).
The code discovery algorithm is based on forced execution and is able to discovery code from one or more entry points. Symbols are optional but can significantly improve the quality of the results. Stripped binaries can pose a challenge for macaw (especially static stripped binaries). Macaw provides support for lifting discovered machine code into an IR suitable for symbolic execution via the Crucible library.
Currently, macaw supports:
The Macaw libraries are:
The libraries that make up Macaw are released under the BSD license.
These Macaw core libraries depend on a number of different supporting libraries, including:
A set of high-level design documents can be found in the doc
subdirectory. Documentation for individual API functions and data types can be
found in the Haddock comments throughout the code.
We have also written some other resources about Macaw:
macaw-symbolic
's lazy memory model (implemented in
Data.Macaw.Symbolic.Memory.Lazy
Dependencies for building Macaw that are not obtained from Hackage are supported via Git submodules:
$ git submodule update --init
The RISC-V backend depends on softfloat-hs, which in turn depends on the
softfloat library. Macaw's build system will automatically build softfloat,
but the softfloat-hs repo must be recursively cloned to enable this. If you
are not building macaw-riscv
you can skip this step. To recursively clone
softfloat-hs, run:
$ cd deps/softfloat-hs
$ git submodule update --init --recursive
The Macaw libraries can be individually built or collectively built with Cabal:
$ ln -s cabal.project.dist cabal.project
$ cabal configure
$ cabal build all
To build a single library, either specify that library name instaed of
all
, or change to that library's subdirectory before building:
$ cabal build macaw-refinement
or
$ cd refinement
$ cabal build
We use the cabal.project.freeze.ghc-*
files to constrain dependency versions
in CI. To build with a known-working set of Hackage dependencies:
ln -s cabal.GHC-<VER>.config cabal.project.freeze
These freeze files were generated using the scripts/regenerate-freeze-files.sh
script.
Note that at present, these configuration files assume a Unix-like operating
system, as we do not currently test Windows on CI. If you would like to use
these configuration files on Windows, you will need to make some manual changes
to remove certain packages and flags:
regex-posix
tasty +unix
unix
unix-compat
Note that if any of the macaw packages fail to build without the freeze files,
it is a bug in the dependency version bounds specified in the .cabal
files
that should be reported (https://github.com/GaloisInc/macaw/issues).
This code is made available under the BSD3 license and without any support.