From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Ales Novak <alnovak@suse.cz>
Cc: gdb@sourceware.org, Peter Griffin <peter.griffin@linaro.org>,
Michael Holzheu <holzheu@linux.vnet.ibm.com>
Subject: Re: gdb on Linux Kernel dumps (gdb-kdump)
Date: Tue, 22 Sep 2015 17:56:00 -0000 [thread overview]
Message-ID: <m3lhbyl4na.fsf@oc1027705133.ibm.com> (raw)
In-Reply-To: <alpine.LSU.2.03.1509172241551.813@suse.cz> (Ales Novak's message of "Thu, 17 Sep 2015 22:47:36 +0200 (CEST)")
On Thu, Sep 17 2015, Ales Novak wrote:
> Hello,
>
> as was discussed at Andreas Arnez's talk during the GNU Cauldron 2015,
> it would be nice to be able to work with Linux kernel dumps using the
> ordinary gdb.
Agreed ;-)
> [...]
>
> The gdb-kdump should be considered rather as a proof of concept, yet it
> shows that enabling the kdumps in gdb should be principally easy. It is
> able to open the x86_64 and s390x kdumps. I'd imagine that most of the
> commands of the crash-utility could be reimplemented using the gdb's
> Python interface.
Right. As pointed out in the talk at the Cauldron, there are already a
few examples in the Linux kernel source tree under "scripts/gdb". In
addition, this post mentions another GDB-enhancing project for Linux
kernel debugging, named "LKD":
https://sourceware.org/ml/gdb-patches/2015-06/msg00040.html
The LKD project focuses more on live debugging and thus might be a
useful complement to gdb-kdump.
>
> The example session looks like that:
>
> [...]
Very nice!
> We'd be thankful for any comments!
IMHO, it would be very useful if GDB had support for various Linux
kernel dump formats and for the Linux kernel runtime. It seems that
gdb-kdump covers both to some extent.
So, how to continue? Would you be able to convert gdb-kdump into
patches against upstream GDB and send those to the gdb-patches mailing
list?
--
Andreas
next prev parent reply other threads:[~2015-09-22 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 20:47 Ales Novak
2015-09-22 17:56 ` Andreas Arnez [this message]
2015-09-22 22:10 ` Ales Novak
2015-09-22 22:48 ` Mike Frysinger
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=m3lhbyl4na.fsf@oc1027705133.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=alnovak@suse.cz \
--cc=gdb@sourceware.org \
--cc=holzheu@linux.vnet.ibm.com \
--cc=peter.griffin@linaro.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