From mboxrd@z Thu Jan  1 00:00:00 1970
From: ksashtekar@gmail.com (Kaustubh Ashtekar)
Date: Thu, 7 Apr 2011 08:40:19 +0530
Subject: Interpreting call trace
In-Reply-To: <BANLkTi=hNu5NV_6e+4Vg0wc1j0ySsDJJdg@mail.gmail.com>
References: <BANLkTi=hNu5NV_6e+4Vg0wc1j0ySsDJJdg@mail.gmail.com>
Message-ID: <BANLkTimVpnd1892Qs6pjyigQB_MtTfY79A@mail.gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

Hi Daniel,

On Wed, Apr 6, 2011 at 6:26 PM, Daniel Baluta <daniel.baluta@gmail.com> wrote:
> Hello,
>
> I have the following stack trace:

<snip>

> How could one interpret this?
>
> For example having:
> [ 3992.316/0] ?[<ffffffff81297751>] ? neigh_create+0x2f1/0x6b0
> [ 3992.321/0] ?[<ffffffff81374f00>] ? _read_unlock_bh+0x10/0x20
>
> means that _read_unlock_bh has been called & finished ? Or it has been
> interrupted by
> next function in trace (neigh_create).

This means that  _read_unlock_bh called neigh_create. The instruction
at (_read_unlock_bh+0x10) will be executed next when the CPU returns
from the function
neigh_create.

For better understanding you can do
> gdb vmlinux
and then run
gdb> disassemble _read_unlock_bh

Then look at offset 0x10.

Kaustubh