From: ksashtekar@gmail.com (Kaustubh Ashtekar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Interpreting call trace
Date: Thu, 7 Apr 2011 08:40:19 +0530 [thread overview]
Message-ID: <BANLkTimVpnd1892Qs6pjyigQB_MtTfY79A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=hNu5NV_6e+4Vg0wc1j0ySsDJJdg@mail.gmail.com>
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
next prev parent reply other threads:[~2011-04-07 3:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 12:56 Interpreting call trace Daniel Baluta
2011-04-06 16:47 ` Michael Blizek
2011-04-06 17:32 ` Mulyadi Santosa
2011-04-07 3:10 ` Kaustubh Ashtekar [this message]
2011-04-07 8:26 ` Daniel Baluta
2011-04-07 9:16 ` nilesh
2011-04-07 9:34 ` Sowmya Sridharan
2011-04-07 17:04 ` Manish Katiyar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTimVpnd1892Qs6pjyigQB_MtTfY79A@mail.gmail.com \
--to=ksashtekar@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).