callgraph-tracer

Trace cross-module function call chains across DeepExtractIDA databases and output JSON or Mermaid diagrams.

17|3|Updated Feb 22, 2026

Search Tags:#diagram #cross-module #xref #callgraph #decompiled-code #analysis-dbs

Ready to run

npx skills add https://github.com/marcosd4h/DeepExtractRuntime --skill callgraph-tracer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: callgraph-tracer
Source: https://github.com/marcosd4h/DeepExtractRuntime/tree/main/skills/callgraph-tracer
Command: npx skills add https://github.com/marcosd4h/DeepExtractRuntime --skill callgraph-tracer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Trace execution flow and cross-module function call chains across DeepExtractIDA analysis databases by following outbound xrefs across DLL boundaries to retrieve decompiled code at each step.

Core Features & Use Cases

Trace outbound xrefs across DLL boundaries and retrieve decompiled code for each step.
Resolve internal vs external calls using the module tracking DB to map cross-module dependencies.
Generate diagrams (Mermaid/DOT) of call graphs and subgraphs for debugging, security reviews, and architecture insights.

Quick Start

Run python chain_analysis.py <db_path> <function_name> to start tracing a function across modules.

Frequently Asked Questions about callgraph-tracer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I trace cross-module function calls across DLL boundaries?▼

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.

What is a cross-module call graph and when do I need it for decompiled code?▼

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.

How do I generate Mermaid or DOT diagrams from decompiled code analysis databases?▼

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.

Do I need per-module analysis databases to trace cross-module execution flow?▼

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.

Can I limit the depth of call graph traversal when tracing xrefs across binaries?▼

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.

What's the best way to visualize cross-module dependencies for security reviews?▼

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.