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

Re: Deciphering Call Trace details

To: "Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx>
Subject: Re: Deciphering Call Trace details
From: Wenhua Zhao <whzhao@xxxxxxxxx>
Date: Thu, 12 Jun 2008 09:15:01 -0700
Cc: "jasjit singh" <singh.jasjit@xxxxxxxxxxx>, kernelnewbies <kernelnewbies@xxxxxxxxxxxx>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:to:cc:subject :references:from:date:in-reply-to:message-id:user-agent:mime-version :content-type; bh=/mzW7hyurJ7Mi3z9e8oBZdHtXZ/CEZWY6ZIDdtV9IDs=; b=Luy3wl9UEsH7AMBCtxyrtzxUeR49R4HcjJL4ZZZtgTkEOoTiDcx+m0TOCGQEPrVmkG UW2Lt+b842xQGjvCe8RTs0L+PTovxvjJ8dtzq6PK5vFGQZtnKBh9LMQPMXKevVHJeAHM jxvlFJivjQR5UHsBWAODSHys1pisVsS9ljZ/M=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=to:cc:subject:references:from:date:in-reply-to:message-id :user-agent:mime-version:content-type; b=lm56EhgsJCtWKsmEiQO06X5roNcNclkdG7HQtT52Q8Hp6bTWlJOEZ2OgEH0yM7H0Fj 7NFPmpWNQ1dyE4TPYY5HmeZK7Edo1ehHMDQdET/YE3PYIELvfutqTGN2FWvKuBJt3MPB Q3YlFZCPcxmnHxuxWhj1vb0dXul9Kl6z6T1Ho=
In-reply-to: <f284c33d0806120633j5b708967k4de97317207f7aaa@mail.gmail.com> (Mulyadi Santosa's message of "Thu\, 12 Jun 2008 20\:33\:25 +0700")
List-archive: <http://mail.nl.linux.org/kernelnewbies/>
List-help: <mailto:ecartis@nl.linux.org?Subject=help>
List-id: <kernelnewbies.nl.linux.org>
List-owner: <mailto:ecartis-owner@nl.linux.org>
List-post: <mailto:kernelnewbies@nl.linux.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:kernelnewbies-request@nl.linux.org?Subject=subscribe>
List-unsubscribe: <mailto:kernelnewbies-request@nl.linux.org?Subject=unsubscribe>
References: <76338.93750.qm@web94003.mail.in2.yahoo.com> <f284c33d0806120633j5b708967k4de97317207f7aaa@mail.gmail.com>
Sender: kernelnewbies-bounce@xxxxxxxxxxxx
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)

Hi,

"Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx> writes:

> 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...
>

If you have you kernel compiled with the debug enabled, then you can
do

objdump -S vmlinux

It will interleave the source with the compiled assembly
instructions.  Very easy to locate the problem.


Regards,
Wenhua

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

References:
- Deciphering Call Trace details
  - From: jasjit singh
- Re: Deciphering Call Trace details
  - From: Mulyadi Santosa

Prev by Date: Re: Regarding Page Swap out
Next by Date: Re: Deciphering Call Trace details
Previous by thread: Re: Deciphering Call Trace details
Next by thread: Re: Deciphering Call Trace details
Index(es):
- Date
- Thread