mix mob.trace_otp (mob_dev v0.3.33)

Copy Markdown View Source

Runs MobDev.OtpTrace.Harness under full call tracing and reports the runtime modules + MFAs actually exercised.

This is the empirical complement to mix mob.audit_otp (which uses static reachability). Combined, they give a high-confidence answer to "what does any Elixir runtime actually need."

Usage

mix mob.trace_otp                 # Run all phases, summary report
mix mob.trace_otp --phase otp     # Just one phase
mix mob.trace_otp --json out.json # Machine-readable dump

Phases

language     — pattern match, comprehensions, structs, protocols
collections  — Enum, List, Map, MapSet, Stream, Range
strings      — String, Binary, charlist, codepoints
processes    — spawn, send/receive, monitor, link, Task
otp          — GenServer, Supervisor, Application, Logger
data         — ETS, persistent_term, Date/Time, System
errors       — raise/rescue, throw/catch, exit, exception structs
all          — every phase (default)

Output

Plain mode prints a summary + sorted module list. --json writes a JSON file with the full MFA set, suitable for cross-referencing against the static audit (mix mob.audit_otp) to find modules shipped-but-never-called.