Lancelot

intel x86(-64) code analysis library that reconstructs control flow

dependencies

• make
• cmake
• pkg-config

Consider using cranelift during development:

$ rustup component add rustc-codegen-cranelift-preview --toolchain nightly
$ env CARGO_PROFILE_DEV_CODEGEN_BACKEND=cranelift cargo build -Zcodegen-backend

Also consider using mold:

$ mold -run cargo build
# or with cranelift:
$ env CARGO_PROFILE_DEV_CODEGEN_BACKEND=cranelift mold -run cargo build -Zcodegen-backend

If it doesn't work with your (read: Willi's) nix setup, use it just for incremental builds.

WebAssembly

the core library (including the zydis-based disassembler) builds for wasm32-unknown-unknown, so lancelot can run entirely in the browser. the bundled Zydis C library is cross-compiled by clang via cmake, which needs a toolchain file so that cmake doesn't try to link executables during its compiler sanity checks:

$ rustup target add wasm32-unknown-unknown
$ CMAKE_TOOLCHAIN_FILE=$(pwd)/wasm32-toolchain.cmake \
    cargo build -p lancelot --target wasm32-unknown-unknown

this requires clang (gcc can't emit wasm) and cmake.

the jslancelot package wraps this wasm build with JavaScript bindings for npm, usable from both Node and the browser.

maintenance

$ rustup update  # update rust compiler

$ cargo update  # update dependencies, not crossing major versions

$ cargo outdated -x unicorn  # find outdated major version dependencies

because we use an older version of unicorn thats easier to build with cargo, we want to ignore any old dependencies stemming from unicorn.

testing

$ pre-commit run --all-files --hook-stage manual