Difference between revisions of "Exception Analysis tools"
(→Outline) |
(→Debugging the kernel) |
||
Line 37: | Line 37: | ||
* debuggers: | * debuggers: | ||
** gdb | ** gdb | ||
+ | ** kdb (local interactive kernel debugging) | ||
+ | |||
+ | * See http://kernel.org/pub/linux/kernel/people/jwessel/dbg_webinar/State_Of_kernel_debugging_LinuxCon2010.pdf | ||
+ | ** Jason Wessel description of kernel debugging status at LinuxCon 2010. |
Revision as of 15:32, 6 June 2011
There are lots of tools for Linux for analyzing and debugging exceptions in both the kernel and user-space programs.
Outline
- capturing information
- information emitted to kernel buffer
- serial console, net console, (other consoles - USB?)
- Oops savers: mtdoops, pstore, ramoops, netoops
- process exceptions
- android tombstones (exception summaries)
- Sony exception monitor log
- coredumps (full process image)
- kernel image
- kdump
- see Kernel crash logging and core dump - Kong Wang, Redhat, at LinuxCon Japan 2011
- kdump
- information emitted to kernel buffer
- parsing information
- oops analysis: http://madwifi-project.org/wiki/DevDocs/KernelOops
- GDB is used with coredump files
- see GDB#Core_dump
- For Sony's EM log: emlogconv, em-log-process
- debuggerd analysis
- interactive analysis
- Sony exception monitor
Debugging the kernel
(this section is only here temporarily)
- target agents:
- connectors:
- adb
- what do WR, MV and others use to set up or connect the debugger to the process?
- debug agents
- gdbserver
- kgdb
- connectors:
- host agents:
- adb server
- debuggers:
- gdb
- kdb (local interactive kernel debugging)
- See http://kernel.org/pub/linux/kernel/people/jwessel/dbg_webinar/State_Of_kernel_debugging_LinuxCon2010.pdf
- Jason Wessel description of kernel debugging status at LinuxCon 2010.