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]

Message-ID: <m1eiyobei1.fsf@fess.ebiederm.org>
Date:	Tue, 27 Jan 2009 13:55:34 -0800
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Dave Anderson <anderson@...hat.com>
Cc:	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?

Dave Anderson <anderson@...hat.com> writes:

> 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.
>
> The debuginfo data of kernel modules can be subsequently added to the
> crash session by doing a gdb "add-symbol-file" command for any or all
> kernel modules.  But getting correct line number information for kernel
> modules has been a crap-shoot in the past, depending upon architecture
> and/or kernel version.  For example, they don't work with 2.6.9-based
> RHEL4 x86_64 kernel modules, but work fine with 2.6.18-based RHEL5 x86_64
> kernels.
>
> Looking at Mike's suspect kernel patch list, I don't see anything that
> would have any relationship to the issue.  Perhaps there was a build tool
> change during the same timeframe? 

It look like Mike just built a series of kernels and had a problem,
which should preclude a tool change.

That said.  Does this feature of crash work in 2.6.29?  If not is
there enough interest to track this down, and fix it if it is a kernel
bug?

If we are going to be using these tools we need them working on the
latest and greatest kernels, not some weird enterprise branch, for
fuddy duddies.

Eric
--
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/