~/talk

Debugging Embedded Linux

slides:none on file

Development spends most time debugging, so the proposed approach focuses on concrete experiments: define the problem, list plausible causes, design a single test to verify one cause, run it and commit results. Tools covered include printf debugging (and the risk it masks race conditions), kernel special files under proc/sys, GDB uses, strace, perf and Wireshark/tcpdump for networking. Example: a rain sensor that fails on a slope is fixed by tilting it, not changing radio or power.

AI-written summary · about

  1. 0:00Introduction to Debugging
  2. 1:09Common Debugging Pitfalls
  3. 2:38Avoiding Slip Solutions
  4. 5:38A Structured Methodology
  5. 7:24Debugging a Weather Station
  6. 11:57Methodology Recap
  7. 14:58Printf and Logging
  8. 18:09Log Levels and Systems
  9. 19:40Kernel Debugging Tools
  10. 21:04Strace and Perf Tools
  11. 23:31Network Debugging
  12. 25:36Common Network Issues
  13. 27:28Final Debugging Summary
  14. 30:10Q&A Session
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.