linux-kernel - Re: BISECTED: Re: source line numbers with x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 27 Jan 2009 13:22:39 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	Dave Anderson <anderson@...hat.com>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andi Kleen <andi@...stfloor.org>,
	Bernhard Walle <bwalle@...e.de>, Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	crash-utility@...hat.com, Mike Snitzer <snitzer@...il.com>
Subject: Re: BISECTED: Re: source line numbers with x86_64 modules?

On Tue, 27 Jan 2009 16:00:19 -0500 (EST)
Dave Anderson <anderson@...hat.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/