TopGit
GitHub Repo Review

RAD Debugger: Epic Games Windows x64 Graphical Debugger

EpicGames/raddebugger
RTopGit review image for EpicGames/raddebugger
Review by Topgit.dev for EpicGames/raddebugger, with GitHub repository stats and README context.
Quick verdict

The RAD Debugger is worth trying if you work on enormous Windows x64 C/C++ projects where Visual Studio's debugger feels sluggish. The native RDI format eliminates on-demand PDB conversion during debug sessions, and the RAD Linker's large-page mode delivers measurable speedups on huge binaries. Skip it if you need cross-platform debugging today or if your projects are small enough that startup latency doesn't matter — and definitely do not use alpha software as your only debugging tool.

Stars
★ 8.8k
Forks
⑂ 467
Contributors
👥 24
Language
C
License
MIT
Topic
—
Updated
Nov 2026
Homepage
—
GitHub

What is the RAD Debugger?

The RAD Debugger is a native graphical debugger for Windows x64, built by Epic Games in C and released under the MIT license. It attaches to user-mode processes, parses PDB files by converting them to a custom RDI format on the fly, and presents a frontend for stepping, inspecting registers, evaluating expressions, and browsing debug info. The project also ships the RAD Linker, a PE/COFF linker that generates standard PDBs alongside optional native RDI output, and the radbin CLI for converting and dumping debug formats.

Key features of the RAD Debugger

  • ✓Native Windows x64 user-mode debugging with multi-process support and graphical frontend
  • ✓Custom RDI (RAD Debug Info) format: PDBs are converted on-demand, eliminating conversion latency during debug sessions
  • ✓Expression evaluator with lexer, parser, type-checker, and IR for inspecting variables, registers, and types
  • ✓Asynchronous debug info streaming and caching to keep the UI responsive on large projects
  • ✓RAD Linker with 50% faster link times on gigabyte-scale debug info and optional large-page mode (25% additional speedup)
  • ✓Graphical visualization engine for watch tables and structured data inspection
  • ✓Self-contained codebase organized into reusable library layers (lib_rdi, lib_codeview, lib_elf, lib_coff, lib_dwarf)
  • ✓MIT licensed, with pre-built Windows binaries available from GitHub releases
How this repository's GitHub stars have grown over time. Source: star-history.com.View the star history ↗

Installing the RAD Debugger

Download pre-built Windows x64 binaries from the releases page on GitHub. Alternatively, build from source: on Windows, install Microsoft C/C++ Build Tools v15 or later, open an x64 Native Tools Command Prompt, run `vcvarsall.bat x64`, then execute `build` for a debug build or `build release` for an optimized build. On Linux, install GCC or Clang plus development packages for freetype, X11, and OpenGL, then run `./build.sh`. Both scripts can also build the RAD Linker (`build radlink release`) and radbin utility (`build radbin release`).

What makes RAD Debugger值得一试

  • ✓Windows x64 debugging pipeline is solid and actively used on real projects at Epic Games
  • ✓RDI format handles gigabyte-scale debug info without the overflow issues that plague 32-bit PDB tables
  • ✓RAD Linker is measurably faster than MSVC on huge linking jobs, with large pages squeezing out another 25%
  • ✓Layered, library-first design means the expression evaluator, COFF parser, and DWARF parser can be reused independently
  • ✓MIT license and self-contained codebase with no external dependencies beyond standard toolchains
  • ✓Pre-built binaries available so you can try it without compiling

Current limitations and alpha status

  • △Alpha software — crashes and missing features are expected; do not rely on it as your sole debugger
  • △Linux debugging is planned but not implemented; only Windows x64 is supported today
  • △DWARF support is incomplete — the converter exists in src/rdi_from_dwarf but is not functional
  • △Debug info is limited to PDB; native DWARF loading requires finishing the ELF-to-RDI pipeline
  • △No Visual Studio integration — you must use the standalone debugger or launch via CLI
  • △Linux builds currently produce a debugger binary but the local debugging backend has not been ported
View on GitHub ↗

RAD Debugger alternatives

Visual Studio Debugger — the standard Windows x64 debugger, deeply integrated with the IDE and ecosystem but heavier on large projectsWinDbg — Microsoft's command-line and graphical debugger with deep kernel support, older UI, and no native RDI pipelineGDB — the GNU debugger, cross-platform and scriptable, but primarily targets Linux and lacks a polished graphical frontend on WindowsLLDB — LLVM's debugger with DWARF-native support, cross-platform, but Windows support is limited compared to its Linux support

Who should try the RAD Debugger

Pick up the RAD Debugger if you are working on Windows x64 C/C++ projects with gigabyte-scale debug info, particularly if you have encountered PDB overflow or PDB loading bottlenecks in Visual Studio. It is also worth a look if you are building custom debugging tooling and want to reuse Epic's parsers for COFF, ELF, DWARF, or CodeView formats. Do not reach for it if you need Linux debugging, production stability, or Visual Studio integration today — watch the roadmap instead.

Frequently asked questions

Is the RAD Debugger production ready?

No — the README explicitly marks it as alpha. Epic asks users to report issues with dump files and reproduction steps to help stabilize it before production use.

What platforms does the RAD Debugger support?

Currently only Windows x64 for debugging. Linux binaries can be built but local Linux debugging is not implemented yet.

Does RAD Debugger support DWARF debug information?

Not yet — the README mentions a partial DWARF-to-RDI converter in src/rdi_from_dwarf, but it is not functional and DWARF support is listed as a future milestone.

Can I use the RAD Debugger on Linux?

You can compile the codebase on Linux with GCC or Clang, but the Linux debugging backend has not been ported yet, so local Linux debugging is not available.

What is the RDI debug info format?

RDI (RAD Debug Info) is Epic's custom debug format defined in src/lib_rdi. PDB files are converted to RDI on-demand, and the RAD Linker can emit native RDI directly to skip conversion during debug sessions.

How fast is the RAD Linker compared to MSVC link?

On test cases with multi-gigabyte debug info, the README reports 50% faster link times than MSVC. Enabling large pages adds another 25% speedup, though large pages are only safe in Docker or VM environments.

The problem it solves

Visual Studio's debugger struggles with the debug info bloat that comes with enormous codebases like Unreal Engine, and the standard PDB pipeline introduces latency during each debug session. Existing open-source graphical debuggers lack native Windows x64 performance or deep integration with PE binaries and PDB files.

Best use cases

  • •Debugging Unreal Engine or similarly massive C/C++ codebases where debug info exceeds several gigabytes
  • •Iterating on PE/COFF binaries where PDB overflow or slow loading bogs down the compile-debug cycle
  • •Teams that want a fast, purpose-built Windows x64 debugger without Visual Studio's overhead
  • •Using the RAD Linker on Docker or VM images where large pages are safe to enable (normal Windows environments risk memory fragmentation)
  • •Building custom debugging tooling on top of reusable components like the expression evaluator, DWARF parser, or COFF/ELF parsers
  • •Replacing broken PDBs in huge executables by generating native RDI debug info directly in the linker
Source & attribution

Source: https://github.com/EpicGames/raddebugger

GitHub data · last synced Oct 9, 2026Reviewed by Henry
← Back to TopGit

Want a second opinion on raddebugger?

Ask an AI that can read this page — one click and you get its take on raddebugger.

GitHub