Kernel Debugging: ftrace, kprobes, dyndbg, kgdb, kdump

When to use

• Debugging kernel crashes, hangs, or wrong behavior where the agent proposes instrumenting the kernel instead of guessing the cause.
• Writing/using ftrace (function_graph, tracepoints), kprobes, dynamic debug (pr_debug), kgdb/kdb, or kdump/crash workflows.
• Reviewing kernel-debug advice for invented files, sysctls, or syntax.
• Interpreting /proc/kallsyms, /proc/iomem, /sys/kernel/tracing/*, /sys/kernel/debug/*.

When not to use

• Kernel internals behavior (scheduler/MM/VFS claims) — use kernel-scheduler-mm-vfs-internals.
• User-space debugging (gdb/ASan) — use dwarf-debug-info, sanitizer-report-reading, crash-triage.
• Containers/cgroups — use kernel-container-internals.