Re: Deciphering Call Trace details

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi...

On Thu, Jun 12, 2008 at 7:23 PM, jasjit singh <singh.jasjit@xxxxxxxxxxx> wrote:
>
> My question is how I can decipher the constant values that are added to
> (perhaps) function pointers.
> e.g  412 in {chrdev_open+412}.

that's...IIRC.... the offset from the beginning of function.

> Can these figures be actually helpful in getting what exactly caused kernel
> to panic ?

yes, just disassemble your vmlinux file...

> And I am not a hardware specialist. Can I use the values of stack and
> various CPU registers to my help ? If yes, then how ?

stack represent the condition of your local variables and passed
parameters, whileCPU registers.....it depends on currently executed op

regards

Mulyadi.

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux