mirror of
https://github.com/lifting-bits/mcsema
synced 2026-06-08 15:31:09 +00:00
Mike Myers
f5cce245f7
* Docs: add content, fix typos, fix formatting * Rename doc file: Mcsema -> McSema * Add a standard Contributing Guidelines doc * Add remarks on verifying McSema, and unit tests
1.7 KiB
1.7 KiB
McSema Command Line Reference
mcsema-disass
Usage: mcsema-disass --disassembler path-to-IDA --os operating-system --arch architecture --output cfg-path --binary input-binary --entrypoint function [--log_file log-path]
Where:
path-to-IDA= the path to your IDA Pro disassembler executable, e.g.,~/ida-6.9/idal64operating-system= the OS of the binary being disassembled:linux, orwindowsarchitecture= the instruction set architecture of the binary being disassembled:amd64,amd64_avx,x86,x86_avx, oraarch64(64-bit ARMv8)cfg-path= the path a .cfg file where you want the recovered control flow graph to be savedinput-binary= the path to a binary executable to be disassembledfunction= the entry point function where the disassembler should start recovering control flow, e.g.,mainlog-path= (optional) the path to a log file to save the logging output of McSema
mcsema-lift
Usage: mcsema-lift --arch architecture --os platform --cfg cfg-path [--output output-path]
Where:
architecture= architecture to use for the instruction semantics during lifting:amd64,amd64_avx,x86,x86_avx, oraarch64(64-bit ARMv8)platform= the operating system of the binary that was disassembled to generate this CFG. Currently the valid options arelinuxorwindows. This option is required for certain aspects of translation, like ABI compatibility for external functions, etc.cfg-path= path to the control flow graph file emitted bymcsema-disassthat you want to convert into bitcodeoutput-path= path to a .bc file where you want the lifted code to be saved. If the--outputoption is not specified, the bitcode will be written to stdout