Rust’s Call Graph Analyzer traces possible panic paths
Tweede golf and Microsoft developed Call Graph Analyzer to trace possible Rust panic paths through application and dependency code. It examines compiler intermediate code after generic functions become concrete implementations, so it can see paths a source-only check misses. Analysis happens before some later optimizations remove unreachable code, however, so a reported path can be a false positive rather than a reachable crash.
Tweede golf · Oct 27, 2026
Why it matters
Embedded and service engineers can review hidden panic paths and detect regressions without treating every diagnostic as a confirmed failure.
More context
The October 27 article links the MIT-licensed project. Building and running the tool uses its pinned nightly compiler and requires build-std compatibility. Try cargo cga check on a small binary or exported library entry point and inspect the call trace.
Keep in mind
The project warns that unstable compiler internals make it fragile and not exhaustively tested. Allowlists can hide paths; external object code and assembly are outside its analysis.
Original read