From: Avi Kivity <avi@redhat.com>
To: Peter Hallberg <hallberg68@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intepreting an oops
Date: Sun, 05 Apr 2009 16:01:28 +0300 [thread overview]
Message-ID: <49D8ABA8.20700@redhat.com> (raw)
In-Reply-To: <COL116-W68F0521CACD2E1656E8D1BDA870@phx.gbl>
Peter Hallberg wrote:
> How does one translate the offset in the function to a line number in the source code?
> [ 218.418473] Call Trace:
> [ 218.418484] [] :nnpfs:nnpfs_writepage+0xab/0x230
>
You can use 'objdump -Sr nnpfs.ko' and look for the address of
nnpfs_writepage, plus 0xab.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-04-05 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 12:48 Intepreting an oops Peter Hallberg
2009-04-05 13:01 ` Avi Kivity [this message]
2009-04-05 14:43 ` Bob Copeland
2009-04-05 15:18 ` Arjan van de Ven
2009-04-07 8:50 ` Michal Hocko
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=49D8ABA8.20700@redhat.com \
--to=avi@redhat.com \
--cc=hallberg68@hotmail.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.