Re: Deciphering Call Trace details

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

 



Le Thu, 12 Jun 2008 17:53:18 +0530 (IST),
jasjit singh <singh.jasjit@xxxxxxxxxxx> a écrit :

> My question is how I can decipher the constant values that are added
> to (perhaps) function pointers. e.g  412 in {chrdev_open+412}.
> Can these figures be actually helpful in getting what exactly caused
> kernel to panic ?

Yes. See Documentation/oops-tracing.txt for an introduction.

Sincerly,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

Attachment: signature.asc
Description: PGP signature


[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