How epicgamesext/raddebugger works
Overall Structure and Main Components
• Within the Debugger subsystem, include major components such as:
• Core Debugger Engine (from layers like “dbg_engine”, “ctrl”, “demon”, “dbgi”)
• Debug Info Conversion and Handling (the “rdi_from_pdb”, “rdi_from_dwarf”, “rdi_dump”, “lib_rdi_format”, “lib_rdi_make” layers)
• Expression Evaluation and Visualization (from “eval” and “eval_visualization”)
• Auxiliary services like asynchronous processing (“async”), file and data caching (“file_stream”, “hash_store”, “geo_cache”, “text_cache”, “texture_cache”, “font_cache”), and code parsing (e.g., “codeview”, “coff”, “msf”, “pdb”).
• OS and Graphics Abstraction layers (from “os/core”, “os/gfx”, “font_provider”)
• Core Linker functionality (organized within the “linker” folder – which includes a number of files handling object files, symbol tables, exports/imports, etc.)
• Integration with debug info generation (show using parts of the RDI system)
• Support for threading and performance optimizations (e.g., use of thread pools in “linker/thread_pool”)
Component Relationships and Interactions
• That both subsystems rely on a core “Base” layer (the “base” folder) which provides utilities for memory management, command-line parsing, logging, and profiling.
• How the Debugger’s core engine drives the UI components, sending commands and receiving data from the evaluation layers.
• Asynchronous work system (the “async” layer) as an infrastructure service that multiple components (like disassembly cache “dasm_cache”, file streaming “file_stream”, and geometric/text caches) depend on.
Architectural Patterns and Design Principles
• A layered architecture, with each folder representing a “layer” (which is also reflected in the namespace conventions found in the code – such as ASYNC_, BASE_, CV_, etc.).
• That the layers form a Directed Acyclic Graph (DAG) wherein lower-level layers (such as “base”, “os/core”) provide services on which higher-level layers build.
• Modularity: many layers (especially those prefixed with “lib_”) are designed to be independent and reuseable in other projects.