Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Ales Novak <alnovak@suse.cz>
Cc: Andreas Arnez <arnez@linux.vnet.ibm.com>,
	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 22:48:00 -0000	[thread overview]
Message-ID: <20150922224822.GG27286@vapier.lan> (raw)
In-Reply-To: <alpine.LSU.2.03.1509222359540.813@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]

On 23 Sep 2015 00:10, Ales Novak wrote:
> On 2015-9-22 19:56, Andreas Arnez wrote:
> > 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.
> 
> Yes. The scripts in scripts/gdb/linux can be used, if they match the 
> dumped kernel. LKD sounds interesting, being slightly in overlap with 
> gdb-kdump.
> 
> > 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?
> 
> The github repo is based on the very recent 7.10 release, i.e. it can be 
> applied almost harmlessly. Yet it brings dependance on the libkdumpfile, 
> which in turn brings dependance on liblzo2, libz, libsnappy (these are 
> used in the dump formats), which I don't know how upstream will like. 
> Should I try to send it anyway?

as long as support is behind a configure flag/check, it shouldn't be a
problem.  gdb doesn't generally care about transitive deps either -- in
this case it merely relies on libkdumpfile.  i'd note that libkdumpfile
has all those libs listed as optional too.  its license is GPL, so that
shouldn't be a problem either.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-09-22 22:48 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
2015-09-22 22:10   ` Ales Novak
2015-09-22 22:48     ` Mike Frysinger [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=20150922224822.GG27286@vapier.lan \
    --to=vapier@gentoo.org \
    --cc=alnovak@suse.cz \
    --cc=arnez@linux.vnet.ibm.com \
    --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