From: Dave Anderson <anderson@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: crash/gdb: DW_FORM_strp pointing outside of .debug_str section
Date: Wed, 19 Nov 2014 09:24:28 -0500 (EST) [thread overview]
Message-ID: <1188484563.12277918.1416407068678.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1199595966.12277152.1416407044657.JavaMail.zimbra@redhat.com>
> Hi,
> I have been trying to debug a multi controller hang issue with crash.
>
> It seems that crash works fine on stock ubuntu 14.04 running
> 3.13.0-39-generic. However when I recompile kernel and try to run
> crash on it I get the following error:
>
> crash> mod -s nvme ./nvme.ko
> MODULE NAME SIZE OBJECT FILE
> ffffffffa01d1240 nvme 58727 ./nvme.ko
> crash> add-symbol-file ./nvme.ko 0xffffffffa01d1240
> add symbol table from file "./nvme.ko" at
> .text_addr = 0xffffffffa01d1240
> Reading symbols from /root/mynvme.sriov/nvme.ko...DW_FORM_strp
> pointing outside of .debug_str section [in module
> /root/mynvme.sriov/nvme.ko]
> gdb: gdb request failed: add-symbol-file ./nvme.ko 0xffffffffa01d1240
> crash>
> Any input on what I might have done wrong? Do I need to rebuild the
> crash utility package along with the kernel?
>
> Thanks,
> Kallol
This is the wrong mailing list for crash utility issues. Please send
your queries to crash-utility@redhat.com.
That being said, the "mod -s" command does the add-symbol-file command
behind the scenes. Your discrete "add-symbol-file" command is both
unnecessary and incorrect -- 0xffffffffa01d1240 is the address
of the nvme module's module data structure and not the starting
text address.
Dave Anderson
next parent reply other threads:[~2014-11-19 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1199595966.12277152.1416407044657.JavaMail.zimbra@redhat.com>
2014-11-19 14:24 ` Dave Anderson [this message]
2014-11-18 23:08 crash/gdb: DW_FORM_strp pointing outside of .debug_str section Kallol Biswas
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=1188484563.12277918.1416407068678.JavaMail.zimbra@redhat.com \
--to=anderson@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox