This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Location of vmlinux debuginfo file
- From: Roland McGrath <roland at redhat dot com>
- To: "Scott M. Ferris" <sferris at acm dot org>
- Cc: Mike Mason <mmlnx at us dot ibm dot com>, "Stone, Joshua I" <joshua dot i dot stone at intel dot com>, "Frank Ch. Eigler" <fche at redhat dot com>, SystemTAP <systemtap at sources dot redhat dot com>
- Date: Sat, 12 Aug 2006 16:20:38 -0700 (PDT)
- Subject: Re: Location of vmlinux debuginfo file
> On Fri, Aug 11, 2006 at 12:48:34PM -0700, Roland McGrath wrote:
> >
> > What it does exactly is look first for /boot/vmlinux-REL, then looks for
> > /boot/vmlinux-REL in the path dirs (i.e. /usr/lib/debug/boot/vmlinux-REL),
> > then looks for /lib/modules/REL/vmlinux, then that in the path dirs.
>
> Wouldn't /lib/modules/REL/build/vmlinux make more sense than
> /lib/modules/REL/vmlinux?
No. The build/ subdirectory is a place to find a kernel you built yourself.
There is no reason to think it matches up with other installed bits, and
using it by default is a terribly bad idea. If you are using a kernel you
built yourself, you should use an explicit option (available in the future)
to say where your kernel and modules are.
The /lib/modules/REL/vmlinux name is not where the kernel is usually
installed. But that name under /usr/lib/debug (got via the debuginfo path
setting) is where the complete vmlinux is usually installed when the file
in /boot is not a normal vmlinux ELF file.
Thanks,
Roland