symdis
A CLI tool for disassembling functions from Mozilla crash reports. Given a module identifier and either a function name or an offset, symdis fetches the binary and symbol information from public servers, disassembles the target function, and annotates it with source lines, call targets, and inline frames.
Designed primarily for use by AI agents analyzing Socorro/Crash Stats crash reports, but also useful for manual crash triage and reverse engineering.
Features
- Fetch symbols and binaries from Mozilla's Tecken symbol server, Microsoft's public symbol server, debuginfod servers, the Snap Store (Ubuntu snaps), and Mozilla's FTP archive — with automatic CAB decompression,
.tar.xzextraction,.pkg(XAR/cpio) extraction, and.apk(ZIP) extraction - Not limited to Mozilla modules: Mozilla's crash infrastructure generates
.symfiles from Microsoft PDBs for all modules seen in crash stacks, so Windows system DLLs (ntdll, kernel32, kernelbase, etc.) are fully supported. Other third-party modules may also have symbols available - Windows, Linux, macOS, and Android module support: PE (via section table), ELF (via PT_LOAD segments), and Mach-O (including fat/universal binaries) binary formats; Android support for Fenix (Firefox for Android) and Focus (Firefox Focus) via APK extraction
- Find functions by exact name, substring match (
--fuzzy), or by RVA/offset - Disassemble x86, x86-64, ARM32, and AArch64 code via Capstone
- Annotate instructions with source file/line, resolved call targets (FUNC/PUBLIC/IAT/PLT/dylib imports), and inline function boundaries
- Demangle C++ (Itanium ABI) and Rust symbol names automatically (
--no-demangleto disable) - Highlight a specific offset (e.g., a crash address) in the output
- Graceful degradation: binary+sym gives full annotated disassembly; binary-only gives raw disassembly; sym-only gives function metadata
- Text and JSON output formats (
--format text|json) - Configurable via TOML config file, environment variables, and CLI flags with layered precedence
- Local cache with WinDbg-compatible layout, atomic writes, negative-cache markers, and
_NT_SYMBOL_PATHintegration
Installation
Pre-built binaries (fastest):
From source:
Or clone and build:
Quick Start
# Disassemble the function containing a specific offset, with crash address highlight
# Fuzzy name search
# Linux module with FTP archive fallback
# macOS module (fat/universal binary from PKG archive)
# JSON output
Example Output
Text (default)
Output is abbreviated — the tool prints all instructions in the function.
; Module: xul.dll (xul.pdb / EE20BD9ABD8D048B4C4C44205044422E1)
; Function: IPC::Channel::ChannelImpl::ProcessIncomingMessages(...) (RVA: 0x144c490, size: 0xa57)
; Source: hg:hg.mozilla.org/releases/mozilla-esr140:ipc/chromium/src/chrome/common/ipc_channel_win.cc:0b8c...
; Architecture: x86
; Data sources: binary+sym
;
; .../ipc_channel_win.cc:...:264
0x0144c490: push ebp
0x0144c491: mov ebp, esp
0x0144c493: push ebx
0x0144c494: push edi
0x0144c495: push esi
0x0144c496: and esp, 0xfffffff8
0x0144c499: sub esp, 0xf8
; .../ipc_channel_win.cc:...:269
0x0144c4b8: test cl, cl
...
; [inline] mozilla::UniquePtr<...>::get() const (.../ipc_channel_win.cc:...:305)
; .../mfbt/UniquePtr.h:...:399
0x0144c4d5: mov ebx, dword ptr [edi + 0x8c]
; [end inline] mozilla::UniquePtr<...>::get() const
...
0x0144c801: call 0x1463290 ; IPC::Channel::ChannelImpl::AcceptHandles(IPC::Message&)
...
==> 0x0144c8cd: call dword ptr [0x173b5260] ; [indirect]
0x0144c8d3: add esp, 4
JSON
Commands
| Command | Description |
|---|---|
disasm |
Disassemble a function from a module |
lookup |
Resolve an offset to a symbol, or a name to an address |
info |
Show module metadata |
fetch |
Pre-fetch symbols and binary for a module |
cache |
Manage the local cache (path, size, clear, list) |
Global Options
| Option | Default | Description |
|---|---|---|
--cache-dir <PATH> |
auto-detected | Cache directory path |
--format <FMT> |
text |
Output format: text or json |
--no-demangle |
off | Disable C++/Rust symbol demangling |
-v / -vv |
off | Verbose output (info / debug) |
--offline |
off | Skip network requests; use only cached data |
Configuration
Settings are resolved with layered precedence: defaults < config file < environment variables < CLI flags.
Config File
Location (checked in order):
SYMDIS_CONFIGenvironment variable- Platform default:
%APPDATA%\symdis\config.toml(Windows) or~/.config/symdis/config.toml(Linux/macOS)
[]
= "D:\\SymbolCache\\symdis"
= 48
[]
= [
"https://symbols.mozilla.org/",
"https://msdl.microsoft.com/download/symbols",
]
= ["https://debuginfod.elfutils.org/"]
[]
= "intel" # "intel" or "att"
= 2000
[]
= "text" # "text" or "json"
[]
= 30
= "symdis/0.1.0"
= false
Environment Variables
| Variable | Description |
|---|---|
SYMDIS_CONFIG |
Override config file path |
SYMDIS_CACHE_DIR |
Override cache directory |
SYMDIS_SYMBOL_SERVERS |
Comma-separated symbol server URLs |
DEBUGINFOD_URLS |
Space-separated debuginfod server URLs |
_NT_SYMBOL_PATH |
Windows symbol path (used for cache directory resolution) |
Cache
Downloaded symbol files and binaries are cached locally. The cache directory is resolved in this order:
--cache-dirCLI flagSYMDIS_CACHE_DIRenvironment variable- Config file
[cache] dirsetting _NT_SYMBOL_PATH(Windows) -- uses the cache path fromSRV*<cache>*<server>entries- Platform default (
%LOCALAPPDATA%\symdis\cache,~/.cache/symdis, or~/Library/Caches/symdis)
The cache uses WinDbg-compatible flat layout (<file>/<id>/<file>) so it can be shared with other symbol tools.
Data and Privacy
symdis processes only publicly available data:
- Inputs: Module identifiers (debug file, debug ID, code file, code ID), function names, and offsets — all from the public portions of crash reports on Crash Stats.
- Downloads: Symbol files and binaries from public symbol servers (Mozilla Tecken, Microsoft, debuginfod) and public archives (Mozilla FTP, Snap Store).
- Does NOT process: Minidumps, memory contents, crash annotations, user comments, URLs, email addresses, or any other protected data.
When using symdis — whether manually or through an AI agent — only provide data from publicly accessible crash report fields (stack traces, module lists, release information). Do not pass protected crash report data (such as user comments, email addresses, or URLs from crash annotations) to symdis or to AI tools analyzing crash reports.
For Mozilla's policies on using AI tools in development, see AI and Coding. For contribution guidelines, see CONTRIBUTING.md.
Documentation
- SPEC.md -- Full specification
- IMPLEMENTATION.md -- Phased implementation plan
License
This project is licensed under the Mozilla Public License 2.0.