hence i didn't know much about it. Last night i was going through the
back trace for this oops and got lost while trying to figure the root cause
Keeping track of function calls in large project can be
very perplexing. Right now i'm checking how the call graphs(generated by kscope)
can be useful.
Thanks,
__amit
On Fri, Apr 24, 2009 at 11:02 AM, Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx> wrote:
Hi...
AFAIK, ksymoops is no longer needed since you already see symbols in
On Thu, Apr 23, 2009 at 2:29 PM, amit mehta <amit4g@xxxxxxxxx> wrote:
> Thanks for your replies, i just wanted to know how to debug
> such kernel OOPS, Forget about this particular OOPS, i just wanted to know
> how you proceed further when you get something similar. As Ramesh told,
> 'ksymoops' can be
> helpful.
the oops message itself. Therefore, the tasks left are locating the
offending instructions that (might) cause the trouble. The hex numbers
are the offset of the function currently executed by the processor.
regards,
Mulyadi.
--
"Everyone has a photographic memory. Some people just don't have film."
— Mel Brooks
