From: Louis Bouchard <louis.bouchard@canonical.com>
To: minyard@acm.org, kexec@lists.infradead.org
Subject: Re: Tool for creating full vmcore
Date: Thu, 13 Feb 2014 10:26:16 +0100 [thread overview]
Message-ID: <52FC8FB8.5030702@canonical.com> (raw)
In-Reply-To: <52FBD7C3.4060304@acm.org>
Hello,
Le 12/02/2014 21:21, Corey Minyard a écrit :
> Hello,
>
> I've written a tool that takes an coredump of physical kernel memory and
> converts it to a coredump of virtual kernel memory that can be directly
> used by gdb to debug a kernel.
>
> I was trying to use /proc/vmcore, but that did not include any of
> vmalloc memory or vmemmap, which made it kind of useless. I thought
> about adding all that to the vmcore, but that didn't seem like the
> proper way to do things.
>
> The tool is at https://github.com/cminyard/kdump-tool
Aside from the other opinions already expressed, I think that the name collision
is unfortunate and will cause problems.
kdump-tools is all over Debian and Ubuntu. I would suggest to rename your
project to something else.
Kind regards,
...Louis
--
Louis Bouchard
Software engineer, Cloud & Sustaining eng.
Canonical Ltd
Ubuntu support: http://canonical.com/support
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2014-02-13 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 20:21 Tool for creating full vmcore Corey Minyard
2014-02-12 21:42 ` Vivek Goyal
[not found] ` <CADq4U7+K-Zi2Ckb-mfDWFf50Oq7hbTWR6H92=Jx=STqWSJu89g@mail.gmail.com>
[not found] ` <20140213135153.GB30844@redhat.com>
2014-02-13 13:52 ` Vivek Goyal
2014-02-13 16:45 ` Corey Minyard
2014-02-13 17:07 ` Vivek Goyal
2014-02-13 9:26 ` Louis Bouchard [this message]
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=52FC8FB8.5030702@canonical.com \
--to=louis.bouchard@canonical.com \
--cc=kexec@lists.infradead.org \
--cc=minyard@acm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox