From mboxrd@z Thu Jan  1 00:00:00 1970
From: nilesh.tayade@netscout.com (nilesh)
Date: Thu, 07 Apr 2011 14:46:29 +0530
Subject: Interpreting call trace
In-Reply-To: <BANLkTikx4FjSbeqC_Er+PBfZMkNRRN7acA@mail.gmail.com>
References: <BANLkTi=hNu5NV_6e+4Vg0wc1j0ySsDJJdg@mail.gmail.com>
	<BANLkTimVpnd1892Qs6pjyigQB_MtTfY79A@mail.gmail.com>
	<BANLkTikx4FjSbeqC_Er+PBfZMkNRRN7acA@mail.gmail.com>
Message-ID: <1302167789.25802.3.camel@nilesh-desktop>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

Hi Daniel,

On Thu, 2011-04-07 at 11:26 +0300, Daniel Baluta wrote:
> > For better understanding you can do
> >> gdb vmlinux
> > and then run
> > gdb> disassemble _read_unlock_bh
> >
> > Then look at offset 0x10.
> 
> Did that. Is there any way to show disassembled
> output interleaved with source code?
> 
May be you can try taking the 'objdump' of vmlinux (FYI, it will be
quite big in size). Otherwise try taking objdump of specific binary
only.

#objdump -r -D -l -S <binary>
> 
> thank you all for your answers.
> 
> Daniel.

-- 
Thanks,
Nilesh