callgraph-tracer

Cross-module function calls are traced by following outbound xrefs across DLL boundaries within DeepExtractIDA analysis databases, retrieving decompiled code at each step to map dependencies and execution flow. It outputs JSON and generates Mermaid or DOT diagrams.

A cross-module call graph visualizes how function behavior spans multiple binaries. You need it during debugging, security reviews, or architecture analysis to identify cross-module dependencies and trace execution flow across DLL boundaries.

Generate Mermaid or DOT diagrams by running the chain analysis script against per-module analysis DBs and the tracking DB. The script resolves internal vs external xrefs and outputs visual call-subgraph relationships for the traced functions.

Yes, tracing cross-module execution flow requires per-module analysis DBs and a module tracking DB. These databases allow the tracer to resolve internal versus external xrefs and retrieve decompiled code accurately across DLL boundaries.

Yes, the tracer supports depth-bounded traversal to limit how far the call graph traversal follows outbound xrefs across binaries. This constrains the analysis scope and prevents the generated subgraphs from becoming excessively large.

The best way to visualize cross-module dependencies for security reviews is generating Mermaid or DOT diagrams from traced call graphs. This maps outbound xrefs across DLL boundaries and retrieves decompiled code to highlight architectural insights.