Fission

Function Triage Workflow

When analyzing an unknown binary, a reliable first pass is:

1) Start with metadata and discovery

./target/release/fission_cli info <binary>
./target/release/fission_cli list <binary>

2) Pick a candidate function by address

Use list --json if you want machine-readable selection:

./target/release/fission_cli list <binary> --json

3) Validate the boundary via disassembly

./target/release/fission_cli disasm <binary> --addr <ADDR> --function

4) Decompile the function

./target/release/fission_cli decomp <binary> --addr <ADDR>

If you are comparing against the current benchmark / reference surfaces, try the compatibility mode:

./target/release/fission_cli decomp <binary> --addr <ADDR> --ghidra-compat

5) Escalate to inventories or benchmarks when appropriate

• If you need whole-binary machine-readable artifacts, use inventory (see docs/CLI.md).
• If you need corpus-scale comparisons and reports, use benchmark/full_benchmark/.

This site is open source. Improve this page.