Bug#700418: kdump-tools: default debug kernel search path is incorrect
On Thu, Feb 21, 2013 at 09:27:38AM -0500, David Magda wrote:
> On 2013-02-12 09:07, David Magda wrote:
>
> >In /usr/share/doc/kdump-tools/README.Debian the following text appears:
> >
> >4. Debug Kernel
> > You *should* have a debug kernel in order for makedumpfile to process
> > the vmcore file. Without a debug kernel, the transfer process is
> > reduced to using "makedumpfile -d 1". Options:
> > A) If /usr/lib/debug/vmlinux-$(uname -r) exists, kdump-tools will
> > use that kernel.
> > B) Explicitly set DEBUG_KERNEL in /etc/default/kdump-tools to
> > point to your debug kernel.
> > C) None of the above. makedumpfile will still work, but your
> > dumpfile will be larger and take longer to save to disk.
> >
> >However all (?) the default -dbg Debian kernel packages put the kernels
> >in /usr/lib/debug/boot/:
> [...]
> >IMHO it would make sense to change (A) so that things worked automagically.
> >
> >If someone had a truly custom kernel, then tweaking DEBUG_KERNEL per (B)
> >would make sense, but the 'standard' Debian tools should work with the
> >standard Debian kernels.
> >
> >The other options would be to remove the boot/ from the debug kernel path.
>
> Has anyone had a chance to take a look at this and evaluate if it's
> a valid concern, or am I just talking crazy?
Sorry, I agree the defaults should match the Debian defaults. When
kdump-tools was written there was no such Debian default, so we made one
up for the custom distro kdump-tools was originally included in.
That said...it looks like version 3.2.39-1 of the linux package added
some symlinks to /usr/lib/debug.
I'm on the fence about changing kdump-tools - in principle it would be
nice if the defaults didn't have to refer to symlinks, but I haven't
been able to find much time to work on this stuff recently. I welcome a
patch. :)
--
John Wright <jsw@debian.org>
Reply to: