Using Yocto to Debug Embedded Device Crashes
summary
Yocto supports three practical ways to handle crash symbols: shipping full debug packages (example: core-image ~70 MB grows to ~390 MB with debug packages — ~400% overhead), running a debug symbol server via OE debug-info-daemon and build IDs, or using minidebuginfo which inflates that image only to ~73 MB (~4% overhead) and gives symbolic stacks. systemd-coredump logs metadata and exposes coredumpctl list / info / gdb for immediate symbolication, but watch userns/sandboxing and stop_timeout truncation. For kernel crashes use kexec + vmcore + makedumpfile + crash; a 1.6 GB vmcore can compress to ~16 MB with filtering.
AI-written summary · about
chapters (5)
- 0:00Introduction to Yocto debugging
- 1:16Debug symbol management
- 7:49Handling user space coredumps
- 22:37Debugging kernel crashes
- 38:56Q&A and troubleshooting
related talks
42mUsing Yocto to Debug Embedded Device Crashes
46mTools and Techniques to Debug an Embedded Linux System
43mTools and Techniques to Debug an Embedded Linux System
38mEfficient On-Device Core Dump Processing for IoT: A Rusty Implementation
31mIf (oops) { Do_not_panic(); }
28mMinidump to debug end user device crashes
40mI heart the Yocto Project
39mHow to Investigate Issues on Linux Embedded System?