Debugging memory issues with Valgrind and GDB
summary
Valgrind and GDB now integrate so GDB can launch Valgrind with target valgrind (no separate terminal needed): Fedora 38 ships vgdb multi-mode plus a Valgrind Python monitor that lets GDB autocomplete Valgrind commands, change options at a breakpoint, run memcheck and ask Valgrind for defined/undefined bits with memcheck get debits, and stop at exit to inspect leaks. Debuginfod auto-downloads missing debuginfo. Works out of the box but is slightly experimental and currently consumes standard input/output of the debugged process.
AI-written summary · about
chapters (10)
- 0:00Introduction to integration
- 1:07Debugging methodologies
- 2:20New Valgrind features
- 4:08Understanding vgdb multi-mode
- 6:16Setting up Valgrind in GDB
- 8:17Python monitor commands
- 10:07Real-world usage examples
- 12:38Diagnostic analysis
- 15:08Summary and acknowledgments
- 17:18Q&A session
related talks
18mFavourite GDB developers tricks
01h 29mMore GDB wizardry and 8 other essential Linux application debugging tools
01h 29mModern Linux C++ Debugging Tools - Under the Covers
58m“Debugging Linux C++”
01h 10mCool New Stuff in GDB 9, 10 and 11
40mMulticore Debugging with GDB
38mProgrammable debuggers and the Linux kernel (drg...
51mDebugging Go programs with Delve