All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: Dave Anderson <anderson@redhat.com>,
	Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] [makedumpfile] Follow debuginfo link of vmlinux file
Date: Thu, 24 May 2007 12:44:26 -0700	[thread overview]
Message-ID: <4655EB1A.3000704@sgi.com> (raw)
In-Reply-To: <20070524192139.GA4160@suse.de>

Bernhard Walle wrote:
> Hello,
> 
> * Dave Anderson <anderson@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:
> http://sourceware.org/gdb/current/onlinedocs/gdb_16.html#SEC154

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?

Thanks,
 - jay

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

  reply	other threads:[~2007-05-24 19:44 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
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 [this message]
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=4655EB1A.3000704@sgi.com \
    --to=jlan@sgi.com \
    --cc=anderson@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=oomichi@mxs.nes.nec.co.jp \
    /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.