Fission

Troubleshooting

Platform-specific build hints

Linux

Install build-essential (Debian/Ubuntu) or equivalent (gcc, clang, headers).
Some WebView stacks for Tauri require extra packages—follow current Tauri docs for your distro.

macOS

Xcode Command Line Tools: xcode-select --install when the compiler is missing.
If cargo cannot link, confirm clang is on PATH.

Windows

Use the MSVC Rust toolchain (x86_64-pc-windows-msvc) for first-class support.
Ensure WebView2 runtime expectations for desktop builds (see Tauri prerequisites).
Path length issues: enable long paths or keep checkouts shallow when hit by MAX_PATH edge cases.

General build failures

Native toolchain missing: C/C++ toolchain required for native dependencies across the workspace.
Submodules: Clone with submodules (git clone --recurse-submodules) if your error references missing vendored trees.
--locked failures in CI: Local Cargo.lock drift—reproduce with the same Cargo version as CI (Rust 1.85+ stable per project docs).

Tauri / front-end failures

Only needed for crates/fission-tauri:

cd crates/fission-tauri && npm ci
Retry npm run tauri dev / cargo tauri dev per team convention.
Capture both npm and Rust stderr in bug reports.

See Tauri desktop workflow.

Analysis mismatches

If decompilation output looks surprising:

Confirm you use canonical CLI subcommands (info, list, disasm, decomp) rather than deprecated flat invocations.
Try JSON (--json) to capture engine routing or metadata useful for debugging.
For comparative evaluation, prefer benchmark/full_benchmark/ runners over manual GUI copy/paste—see Comparing with Ghidra.

When to escalate

If reproduction requires a private binary, supply hashes, minimal flags, and synthetic equivalents when possible.
Route fixes per AGENTS.md: semantic issues belong in owning crates (fission-pcode, fission-static, …), not only CLI printing.

This site is open source. Improve this page.