LLDB extension supports cross CPU and GPU debugging
The story so far
Meta Engineering has extended LLDB through its neutral accelerator plugin architecture for lldb-server, enabling application debugging across CPUs and GPUs. This architecture separates the general debugging infrastructure from hardware-specific device control, presenting CPUs and GPUs as independent debugging processes that collaborate within a single debugging session. The architecture converts hardware-specific debugging APIs into concepts understandable by LLDB via plugins, supporting collaborative debugging of CPUs and GPUs with different architectures, registers, memory spaces, and execution models while maintaining client neutrality. GPU debugging support is activated only when the debugged application runs on a supported GPU runtime; for applications using only CPUs, LLDB and lldb-server continue through existing native debugging paths without runtime computational overhead. The plugin boundaries are intentionally based on debugger operations rather than specific GPU platform concepts. The framework supports postmortem GPU debugging as well as real-time sessions.
AI-written from the reports · Updated 9 days ago
Coverage timeline
Follow the coverage to see every side of the story.
- Meta EngineeringExtending LLDB to Debug Applications That Span CPUs and GPUs
LLDB supports application debugging across CPU and GPU through the neutral accelerator plugin architecture of lldb-server, separating general debugging infrastructure from hardware-specific device control, presenting CPU and GPU as independent debugging processes that work together in a single debugging session. This architecture converts hardware-specific debugging APIs into concepts understood by LLDB through plugins, supporting collaborative debugging of CPUs and GPUs with different architectures, registers, memory spaces, and execution models while maintaining the neutrality of the client.