Debuggability
summary
Compares GCC and Clang by opening cores in GDB and counting how many local variables a backtrace actually resolves, using DWARF debug sections as the metric. Finds Clang (circa a year ago) often emits DWARF output garbage or nothing even at -O0 so few resolvable locals appear, while GCC reliably produces far more inspectable state. Notes Clang 3.9 improves but still trails GCC in practical debuggability.
AI-written summary · about
chapters (3)
related talks
01h 25mPeeking Into Your Compiler
21mAbstract Debuggers: Exploring Program Behaviors Using Static Analysis Results
37mThe Bright Future of Debuggers: Challenges and Opportunities
59mTheory makes beautiful programs
30mA Series of Unfortunate Bugs
24mSymbiotic: finding bugs in C programs
11mFix your hardest bugs with ease with Time Travel Debugging - Session Interview With Greg Law
40mLessons from two decades of writing bad code