All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ken'ichi Ohmichi" <oomichi@mxs.nes.nec.co.jp>
To: Bernhard Walle <bwalle@suse.de>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] [makedumpfile] Follow debuginfo link of vmlinux file
Date: Thu, 24 May 2007 09:35:56 +0900	[thread overview]
Message-ID: <20070524093556oomichi@mail.jp.nec.com> (raw)
In-Reply-To: <20070501133912.GA8247@suse.de>


Hi Bernhard,

2007/05/01 15:39:12 +0200, Bernhard Walle <bwalle@suse.de> wrote:
>This patch implements support for following the debug information link in the
>.gnu_debuginfo section if the specified binary contains one. That makes it
>possible to call makedumpfile with -x /boot/vmlinux-<version> on distributions
>that ship extra -debuginfo packages for the kernel.

Isn't it good to specify the debuginfo file directly instead of your patch ?
I confirmed that makedumpfile without your patch can run by specifying the
debuginfo file directly.

makedumpfile needs only .debug_info section and doesn't need other sections,
so it needs only the debuginfo file. I will add the following comment to the
manual for "Debugging Information in Separate Files". Please let me know your
opinion.

-------------------------------------------------------------------------------
       -x VMLINUX
              Specify the first kernel’s VMLINUX  with  debug  information  to
              analyze the first kernel’s memory usage.
+             If there is a file containing debug information and separated from
+             VMLINUX, the file should be specified instead of VMLINUX.
              The  page  size of the first kernel and the second kernel should
              match.
              Example:
              # makedumpfile -d 31 -x vmlinux /proc/vmcore dumpfile
-------------------------------------------------------------------------------


Thanks
Ken'ichi Ohmichi

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2007-05-24  0:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 13:39 [PATCH] [makedumpfile] Follow debuginfo link of vmlinux file Bernhard Walle
2007-05-24  0:35 ` Ken'ichi Ohmichi [this message]
2007-05-24  6:54   ` Bernhard Walle
2007-05-24  7:09     ` Bernhard Walle
2007-05-24 17:21   ` Jay Lan
2007-05-24 18:31     ` Dave Anderson
2007-05-24 19:21       ` Bernhard Walle
2007-05-24 19:44         ` Jay Lan
2007-05-24 19:54           ` Bernhard Walle
2007-05-29 11:43     ` Ken'ichi Ohmichi
2007-05-29 17:44       ` Jay Lan
2007-05-29 18:42         ` Bernhard Walle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070524093556oomichi@mail.jp.nec.com \
    --to=oomichi@mxs.nes.nec.co.jp \
    --cc=bwalle@suse.de \
    --cc=kexec@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.