I was able to show how to analyze an oops as follows: prepare an oops in mydriver.ko boot a kernel with debug info. ( prepare it before course ) objdump -Sl mymod.ko | less you will be able to show the exact line of crash. I presented to a few of my colleagues. fast and simple. analyzing an oops is more than essential. it is a must. Raz On Fri, Jul 10, 2009 at 3:37 AM, Leandro Dorileo<ldorileo@xxxxxxxxx> wrote: > Hi Robert > > On Thu, Jul 9, 2009 at 11:19 AM, Robert P. J. Day<rpjday@xxxxxxxxxxxxxx> wrote: >> On Thu, 9 Jul 2009, Mulyadi Santosa wrote: >> >>> 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 >> >> i might be able to throw in a few minutes on how to decode an >> oops, but i doubt i'd have time to get to systemtap or ftrace. i'm >> guessing that would be part of an entire advanced kernel course which >> would cover debugging in detail. > > 30 minutes is really not enough time but it would be really good to > you at least tell systemtap and ftrace does exist, maybe show some > output and scripts. > > regards.... > > -- > (°= Leandro Dorileo > //\ ldorileo@xxxxxxxxx - http://www.dorilex.net > V_/ Software is a matter of freedom. > > -- > To unsubscribe from this list: send an email with > "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx > Please read the FAQ at http://kernelnewbies.org/FAQ > > -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
