debuginfod: get debugging data + sources easily
summary
A lightweight HTTP server indexes RPMs and build trees and serves DWARF debuginfo and source files keyed by build-id lookup, reachable with a single DEBUGINFOD_URLS env var. Clients (gdb, systemtap, perf and more; valgrind support in progress) query the server and automatically fetch missing .debug and source files; demos show systemtap producing call graphs and gdb/valgrind resolving symbols and line numbers. Servers run unprivileged, support federation, expose Prometheus metrics, and are already available on public and distro mirrors.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:15Problem
- 1:29What is debugging info
- 3:48Why debuginfod
- 4:22fedora and rel
- 5:01ubuntu
- 5:42arch linux
- 6:08nyx
- 7:32debuginfod
- 9:20debugging for clients
- 11:10build ids
- 11:43demo
- 16:59links
related talks
32mDebuginfod in Ubuntu
35mRethinking Linux tools with Compact Debuginfo Formats
01h 10mCool New Stuff in GDB 9, 10 and 11
25mDebugging memory issues with Valgrind and GDB
01h 29mMore GDB wizardry and 8 other essential Linux application debugging tools
58m“Debugging Linux C++”
32mCross Debugging on Linux : A History, Current State of the Art and Coming Improvements
52mGetting the Most Out of GDB
