登录 注册
开发者工具
8,834
Stars
—
Forks
0
Watchers
—
Open Issues
待补全
许可证
C
语言
—
创建时间
最近更新

项目能做什么

一款原生、用户态、多进程的图形化调试器。
来源:AI 基于仓库事实生成 · 内容以仓库实际 README 为准

使用说明 查看原始 README 原仓库文档

中文使用说明暂未生成。下面保留原仓库 README 摘录,命令与配置均以原文为准。
原始 README 摘录(英文原文,节选前 3000 字符)
# The RAD Debugger Project

_**NOTE:** This README does not document usage instructions and tips for the
debugger itself, and is intended as a technical overview of the project. The
debugger's README, which includes usage instructions and tips, can be found
packaged along with debugger releases, or within the `build` folder after a
local copy has been built. You can find pre-built release binaries
[here](https://github.com/EpicGames/raddebugger/releases)._

The RAD Debugger is a native, user-mode, multi-process, graphical debugger. It
currently only supports local-machine x64 debugging on both Windows and Linux
(although Linux support is still very early). We plan to expand support to
other architectures, and to implement remote and multi-machine debugging.

The debugger is currently in *ALPHA*. In order to get the debugger
bullet-proof, it'd greatly help out if you submitted the issues you find
[here](https://github.com/EpicGames/raddebugger/issues), along with any
information you can gather, like dump files (along with the build you used),
instructions to reproduce, test executables, and so on.

In addition to the debugger, we aim to further improve the toolchain with two
additional related technologies: **(1)** the RAD Debug Info (RDI) format, and
**(2)** the RAD Linker.

## The RAD Debug Info (RDI) Format

The RAD Debug Info (RDI) format is our custom debug information format, which
the debugger parses and uses, rather than the debug information natively
produced by toolchains, like PDB or DWARF. To work with these existing
toolchains, we convert PDB and DWARF to the RDI format on-demand.

The RDI format is currently specified in code, in the files within the
`src/lib_rdi` folder. In [`rdi.h`](src/lib_rdi/rdi.h) and
[`rdi.c`](src/lib_rdi/rdi.c), the types and functions which define the format
itself are specified. In [`rdi_parse.h`](src/lib_rdi/rdi_parse.h) and
[`rdi_parse.c`](src/lib_rdi/rdi_parse.c), helpers for parsing the format are
included.

We also have an in-progress library for constructing and serializing RDI data,
located within the `src/lib_rdi_make` folder.

Our `radbin` utility (accessible through the debugger too, via the `--bin`
command line argument) is capable of converting native debug information formats
to RDI, and of producing textual dumps of contents stored within RDI files.

## The RAD Linker

The RAD Linker is a new performance linker for generating x64 PE/COFF binaries.
It is designed to be very fast when creating gigantic executables. It generates
standard PDB files for debugging, but it can also (optionally) natively create
RAD Debug Info too, which is useful both to eliminate on-demand conversion time
when debugging, but also for huge executables that otherwise create broken
PDBs that overflow internal 32-bit tables.

The RAD Linker is primarily optimized to handle huge linking projects. In our
test cases (where debug info is multiple gigabytes), we see 50% f
阅读完整原文

项目深度分析 AI 生成

企业级游戏研发工作流/CI集成与商业支持

产品构想基于RAD Debugger和RAD Linker,为中大型游戏工作室提供无缝替换MSVC link.exe的方案实施、构建流水线性能优化以及专家级技术支持服务。
核心功能定制化构建流水线接入方案、崩溃转储(Dump)分析协助、定制格式转换插件、SLA技术响应与补丁维护。
目标用户采用Unreal Engine或自研重型引擎的游戏制作公司、虚拟制作工作室。
难度/周期高 · 3-6个月 · 成本:极高(需要深厚的底层系统编程、编译器和PE/COFF链接器经验)
收费模式年度技术支持服务费(SLA合同)、定制集成咨询服务包。
竞争风险项目隶属于Epic Games官方开源,受其开源协议(当前未明确显示License)与官方更新节奏制约;独立商业实体难以单靠外围服务维持高议价。
依据 已验证事实

RAD Debug Info (RDI) 格式与工具链生态商业组件

产品构想基于lib_rdi开发第三方生态插件,例如为VS Code、CLion或RenderDoc等工具提供超快速解析RDI格式的桥接插件或符号服务器中间件。
核心功能DAP(Debug Adapter Protocol)转RDI中间层协议、IDE端无缝调试适配器、超快速符号缓存服务器。
目标用户习惯VS Code等现代IDE但饱受传统PDB解析过慢折磨的跨平台C/C++开发人员。
难度/周期极高 · 6-12个月 · 成本:高(研发周期长,技术壁垒极高)
收费模式按开发者席位订阅(如IDE Marketplace付费插件)、企业私有符号缓存网关授权。
竞争风险调试器处于ALPHA阶段,内部RDI格式规范变更频繁,维护向后兼容成本极高。
依据 尚需验证的假设

分布式大型二进制链接与调试缓存加速系统

产品构想围绕RAD Linker的大内存页加速和超大项目特性,打造适配混合云构建农场的分布式链接缓存与自动化调优代理系统。
核心功能动态感知构建主机内存/CPU自动配置(/rad_workers、/rad_large_pages自适应)、构建产物与RDI符号表分布式去重分发。
目标用户拥有数千个C++代码仓库、每天执行海量CI编译任务的软件巨头与游戏大厂。
难度/周期高 · 6-9个月 · 成本:中(需要云原生与分布式存储基础设施支持)
收费模式企业级自部署软件授权费用、按构建节点计费的专有代理程序。
竞争风险官方已在提示Windows大内存页有内存碎片风险,工程化规避策略在生产环境中极具挑战性。
依据 数据支持的判断
AI 基于仓库公开数据分析生成,含推测成分,不构成收益承诺。
报告会保存到 个人中心

竞品与相似项目 GitHub Search 真实检索

项目中文简介Stars语言
charlesastaylor/jai-raddebugger 中文介绍暂未生成
Integration with RAD Debugger from jai
24 Jai
brevin33/raddebugger.nvim 中文介绍暂未生成
Rad Debugger integrating for NeoVim (https://github.com/Epic
18 Lua
slendidev/raddebugger-flake 中文介绍暂未生成
Nix flake for raddbg
2 Nix
tom-seddon/raddebugger_build 中文介绍暂未生成
1 CMake
以上为通过 GitHub 官方 Search API 检索的相似项目,功能差异与优劣势需进一步人工确认,配置 AI 后可生成对比分析。

项目优势与风险

技术成熟度创建时间待补全,最近推送 ,发布过 30 个 Release
社区活跃Star 8,834 / Fork 0 / Issue 0(数据支持,可自行核实)
许可证未检测到(需人工确认)
主要风险上游项目方向可能变化;同赛道竞争者较多(见竞品表);热度与需求不完全等价

安装与使用

此项目未提供 Docker 镜像,安装步骤以原仓库 README 为准(涉及依赖安装与环境配置,对新手门槛较高)。