Tools and Techniques to Debug an Embedded Linux System
summary
Shows how kernel oops addresses map to source using addr2line + vmlinux with debug symbols so crashes resolve to exact lines; demonstrates tracing a 4s delay where ftrace + trace-cmd reveals msleep taking 4s and visualizes it with KernelShark; reproduces a user-space hang and pinpoints the culprit with perf + uprobe collecting symbols and perf script; captures core files via ulimit, debugs remotely via kgdb/GDB over serial or gdbserver, and finds leaks with valgrind reporting malloc backtraces (e.g. cpolo.c:79).
AI-written summary · about
chapters (14)
- 0:00Intro
- 2:13THE SIX STAGES OF DEBUGGING
- 3:56DEBUGGING STEP-BY-STEP
- 8:00TOOLS AND TECHNIQUES
- 11:35POST MORTEM ANALYSIS
- 14:47EXAMPLE: KERNEL CRASH (CONT.)
- 23:11EXAMPLE: KERNEL TRACING (CONT.)
- 29:05INTERACTIVE DEBUGGING
- 32:48EXAMPLE: KERNEL DEBUGGING WITH GDB (CONT.)
- 34:00EXAMPLE: USER SPACE DEBUGGING WITH GDB
- 35:37DEBUGGING FRAMEWORKS
- 37:32EXAMPLE: DEBUGGING KERNEL HANGS (CONT.)
- 39:35EXAMPLE: MEMORY LEAKS IN USER SPACE (CONT.)
- 42:08PROBLEMS VS TECHNIQUES (3)
related talks
43mTools and Techniques to Debug an Embedded Linux System
31mIf (oops) { Do_not_panic(); }
39mHow to Investigate Issues on Linux Embedded System?
38mDebugging Embedded Linux
37mDebugging & Tracing and More Between Linux and RTOS on Heterogeneous ARM SoC
42mUsing Yocto to Debug Embedded Device Crashes- 42mUsing Yocto to Debug Embedded Device Crashes
02h 00mAdvanced Debug and Trace Tools for RISC-V Architectures