[PATCH] [makedumpfile] Follow debuginfo link of vmlinux file
oomichi at mxs.nes.nec.co.jp
Tue May 29 07:43:11 EDT 2007
Sorry for the late response.
2007/05/24 12:44:26 -0700, Jay Lan <jlan at sgi.com> wrote:
>Bernhard Walle wrote:
>> * Dave Anderson <anderson at redhat.com> [2007-05-24 20:31]:
>>> The crash utility hides the details of there being a separate debug
>>> file in the same way the gdb does when working with a binary executable
>>> that has a separate debuginfo file. It tries *not* to be ambiguous,
>>> i.e., the point is to stay true to the "crash vmlinux vmcore" model.
>> It's documented in the GDB documentation:
>Thanks for the pointer, Bernhard. I installed kernel-debuginfo rpm
>but crash still failed to find the debug information... I had to
>copy the kernel-<version>.debug to /boot for it to work.
>So, i think it is a good idea for makedumpfile to follow the same
>convension as crash and gdb, Ken'ichi?
No, I don't think it is worthy that a kernel file is specified *only*
for getting the path to a debuginfo file. It is smart to specify
a debuginfo file directly. The crash utility needs both a kernel
file and a debuginfo file, but makedumpfile needs only a debuginfo
file as I said.
BTW, I recommend using a makedumpfile's CONFIGFILE instead of a
debuginfo file. If a system has a CONFIGFILE, makedumpfile can
run without a debuginfo file. It is smaller than a debuginfo file,
and it is easy to distribute it to each system.
I don't think each system should have a debuginfo file, because the
file is big and a user may analyze a dumpfile on a remote analysis
More information about the kexec