Interpreting call trace

Kaustubh Ashtekar ksashtekar at gmail.com
Wed Apr 6 23:10:19 EDT 2011


Hi Daniel,

On Wed, Apr 6, 2011 at 6:26 PM, Daniel Baluta <daniel.baluta at 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



More information about the Kernelnewbies mailing list