From: Arjan van de Ven <arjan@infradead.org>
To: Dave Anderson <anderson@redhat.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Andi Kleen <andi@firstfloor.org>, Bernhard Walle <bwalle@suse.de>,
Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
crash-utility@redhat.com, Mike Snitzer <snitzer@gmail.com>
Subject: Re: BISECTED: Re: source line numbers with x86_64 modules?
Date: Tue, 27 Jan 2009 13:22:39 -0800 [thread overview]
Message-ID: <20090127132239.7087b2f9@infradead.org> (raw)
In-Reply-To: <1457226967.823651233090019084.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com>
On Tue, 27 Jan 2009 16:00:19 -0500 (EST)
Dave Anderson <anderson@redhat.com> wrote:
>
> Actually it's not a problem with the vmlinux file, but rather with
> kernel module object files. The crash utility has an embedded gdb
> module which is invoked as "gdb vmlinux", and to get line numbers,
> the crash utility simply uses the relevant built-in gdb function to
> get them. And line numbers work fine with the base kernel code from
> the vmlinux file.
if the entire goal is to get a pinpoint of where the crash is, just
using scripts/markup_oops.pl will do the right thing.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-01-27 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <952123357.823421233089955989.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com>
2009-01-27 21:00 ` Dave Anderson
2009-01-27 21:22 ` Arjan van de Ven [this message]
2009-01-27 21:55 ` Eric W. Biederman
2009-01-27 23:41 ` Mike Snitzer
[not found] <1298337055.846811233094677227.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com>
2009-01-27 22:20 ` Dave Anderson
2009-01-27 17:09 Mike Snitzer
2009-01-27 19:38 ` Eric W. Biederman
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=20090127132239.7087b2f9@infradead.org \
--to=arjan@infradead.org \
--cc=anderson@redhat.com \
--cc=andi@firstfloor.org \
--cc=bwalle@suse.de \
--cc=crash-utility@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=snitzer@gmail.com \
/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
all inboxes | Powered by JetHome®