On Thu, Jul 9, 2009 at 7:55 PM, Robert P. J. Day<[email protected]> wrote: > > i'm going to leech off of the collective intelligence of this list > for a few minutes. toward the end of a 1-day kernel course i'm > designing, i want to *very* briefly present some kernel debugging > techniques. given the limited time i'm going to have, i can't see > having more than about 20 or 30 minutes for this, so i can't possibly > get into fancy debugging, such as with kgdb, or anything that requires > a kernel config and reboot. so that doesn't leave me a lot of > options. > > i figure the best i can do is talk about SysRq, a number of the > kernel config options that people *could* turn on (under "Kernel > Hacking"), and possibly mounting the debugfs to get access to any > portions of the kernel that bothered to use it. beyond that, i'm > not sure what else could be crammed in there but i'm open to > suggestions. thanks.
I think one of the core skills one should have is how to "decode" oops message. Other options that quickly cross my mind: 1. systemtap. 2. ftrace -- regards, Mulyadi Santosa Freelance Linux trainer blog: the-hydra.blogspot.com -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ
