public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Philipp Rudo <prudo@linux.vnet.ibm.com>
To: Kamil Rytarowski <n54@gmx.com>
Cc: gdb-patches@sourceware.org,
	Omair Javaid <omair.javaid@linaro.org>,
	       Yao Qi <qiyaoltc@gmail.com>,
	arnez@linux.vnet.ibm.com
Subject: Re: [RFC PATCH v5 4/9] Add basic Linux kernel support
Date: Wed, 14 Mar 2018 09:48:00 -0000	[thread overview]
Message-ID: <20180314104809.6732add0@ThinkPad> (raw)
In-Reply-To: <a10f42c5-5f6e-9dce-8373-48de345f0f73@gmx.com>

Hi Kamil,

On Tue, 13 Mar 2018 15:08:32 +0100
Kamil Rytarowski <n54@gmx.com> wrote:

> On 12.03.2018 16:31, Philipp Rudo wrote:
> > Implement the basic infrastructure and functionality to allow Linux kernel
> > debugging with GDB.  This contains handling of kernel symbols and data
> > structures as well as a simple target_ops to hook into GDB.  For the code
> > to work architectures must provide an implementation for the virtual
> > methods in linux_kernel_ops.
> > 
> > For simplicity this patch only supports static targets, i.e. core dumps.
> > Support for live debugging will be provided in a separate patch.
> >   
> 
> 
> What's wrong with kgdb? It works well on NetBSD for alive and dead
> kernels since 90ties.

I don't know kgdb well. We at IBM mostly work with dumps and the crash tool,
which is based on an old version of gdb and has some drawbacks. For example it
doesn't have a dwarf unwinder. That's why we wanted to see if the logic needed
for kernel debugging can be added directly to gdb, instead of having a hack
working on top of it.

Furthermore, I don't see a conflict between kgdb and this work. The way I see
it, kgdb is a technique to retrieve information from the kernel. This work
however, teaches gdb how to interpret the data from the kernel in order to make
it easier to find the information you need.

Thanks
Philipp

  reply	other threads:[~2018-03-14  9:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 15:31 [RFC v5 0/9] Add support for Linux kernel debugging Philipp Rudo
2018-03-12 15:31 ` [RFC PATCH v5 9/9] Add S390 support for linux-kernel target Philipp Rudo
2018-03-12 15:31 ` [RFC PATCH v5 6/9] Add commands " Philipp Rudo
2018-03-12 15:31 ` [RFC PATCH v5 3/9] Add scoped_restore_regcache_ptid Philipp Rudo
2018-03-17 18:08   ` Simon Marchi
2018-03-12 15:31 ` [RFC PATCH v5 4/9] Add basic Linux kernel support Philipp Rudo
2018-03-13 14:09   ` Kamil Rytarowski
2018-03-14  9:48     ` Philipp Rudo [this message]
2018-03-14 23:38       ` Kamil Rytarowski
2018-03-19  0:11   ` Simon Marchi
2018-03-12 15:31 ` [RFC PATCH v5 7/9] Add privileged registers for s390x Philipp Rudo
2018-03-12 15:31 ` [RFC PATCH v5 2/9] Add libiberty/concat styled concat_path function Philipp Rudo
2018-03-16  2:47   ` Simon Marchi
2018-03-12 15:31 ` [RFC PATCH v5 8/9] Link frame_info to thread_info Philipp Rudo
2018-03-12 15:31 ` [RFC PATCH v5 1/9] Convert substitute_path_component to C++ Philipp Rudo
2018-03-16  2:15   ` Simon Marchi
2018-03-17 20:11     ` Simon Marchi
2018-03-12 15:31 ` [RFC PATCH v5 5/9] Add kernel module support for linux-kernel target Philipp Rudo

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=20180314104809.6732add0@ThinkPad \
    --to=prudo@linux.vnet.ibm.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=n54@gmx.com \
    --cc=omair.javaid@linaro.org \
    --cc=qiyaoltc@gmail.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).