public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Amit S. Kale" <akale@veritas.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Paul J Albrecht <pjalbrecht@home.com>,
	linux-kernel@vger.kernel.org, Jeff Dike <jdike@karaya.com>
Subject: Re: Linux Kernel Debuggers, KDB or KGDB?
Date: Tue, 01 May 2001 11:59:17 +0100	[thread overview]
Message-ID: <3AEE9705.CCA13D76@veritas.com> (raw)
In-Reply-To: <18223.988679810@kao2.melbourne.sgi.com>

Hi,

I mostly agree with Keith.

kdb and kgdb have similar capabilities. kgdb can be used
to do kdb like assembly level debugging too, though it
needs some knowledge of gdb and kgdb internals.

You can analyze any problems with either of the debuggers.
You'll need to decide which debugger to go for depending
on your requirements.

I've got many queries asking kgdb capabilities.
I guess it's time for a webpage comparing the two
debuggers. People who are new to linux kernel and
have not used any of the debuggers can hardly arrive
at a decision as to which debugger is better suited for
their work.

I always suggest for kgdb over kdb because, IMO source
level debugging makes a programmers life much easier.

UML too is a good kernel debugging tool. It offers
the advantage of source level debugging on a single
machine. IMHO it's more useful for beginners.

Keith Owens wrote:
> 
> On Mon, 30 Apr 2001 16:17:22 -0500,
> Paul J Albrecht <pjalbrecht@home.com> wrote:
> >Where can I find an analysis of the relative strengths and weaknesses of KDB
> >and KGDB for kernel debug? Has the linux community come to any consensus
> >regarding the utility one or the other?
> 
> kdb is a really low level debugger which understands the kernel
> structures.  It does its utmost to stop all kernel activity while it is
> running and to use as few kernel services as possible so it can run
> even when the kernel is dead.  It (currently) has no source level
> debugging.
> 
> kgdb relies on gdb so you loose the knowledge of kernel internals (no,
> I am *not* going to teach gdb about kernel stacks, out of line lock
> code etc.).  kgdb has more of a dependency on a working kernel.  It
> provides source level debugging, although stack backtrace tends not to
> work unless you compile the kernel with frame pointers.
> 
> UML is great for debugging generic kernel code such as filesystems, but
> cannot be used for most arch code or hardware drivers.
> 
> My ideal debugger is one that combines the internal knowledge of kdb
> with the source level debugging of gdb.  I know how to do this over a
> serial line, finding time to write the code is the problem.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Amit Kale
Veritas Software ( http://www.veritas.com )

  reply	other threads:[~2001-05-01 10:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-30 21:17 Linux Kernel Debuggers, KDB or KGDB? Paul J Albrecht
2001-05-01  0:11 ` Jeff Dike
2001-05-01  9:37   ` Ingo Oeser
2001-05-01 15:22     ` Jeff Dike
2001-05-02 14:44       ` Ingo Oeser
2001-05-02 17:54         ` Jeff Dike
2001-05-02 16:55           ` Alan Cox
2001-05-02 19:06             ` Jeff Dike
2001-05-02 18:54               ` Bill Nottingham
2001-05-01  1:16 ` Keith Owens
2001-05-01 10:59   ` Amit S. Kale [this message]
2001-05-02 14:58   ` Andi Kleen
2001-05-02 21:06   ` Paul J Albrecht
2001-05-02 23:03     ` Keith Owens
2001-05-03 14:46       ` Amit S. Kale
     [not found] <linux.kernel.18223.988679810@kao2.melbourne.sgi.com>
2001-05-01  7:13 ` Aaron Passey

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=3AEE9705.CCA13D76@veritas.com \
    --to=akale@veritas.com \
    --cc=jdike@karaya.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pjalbrecht@home.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