From: Keith Owens <kaos@ocs.com.au>
To: Andrew Morton <akpm@zip.com.au>
Cc: Jeremy Jackson <jerj@coplanar.net>, linux-kernel@vger.kernel.org
Subject: Re: [QUESTION] which kernel debugger is "best"?
Date: Sat, 30 Mar 2002 14:46:02 +1100 [thread overview]
Message-ID: <2178.1017459962@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 29 Mar 2002 19:18:39 -0800." <3CA52E8F.C8D0E5F8@zip.com.au>
On Fri, 29 Mar 2002 19:18:39 -0800,
Andrew Morton <akpm@zip.com.au> wrote:
>Jeremy Jackson wrote:
>>
>> What are people using?
>
>kgdb. Tried kdb and (sorry, Keith), it's not in the same
>league. Not by miles.
kdb and kgdb are aimed at different debugging environments. kgdb
requires a second machine containing the kernel compiled with -g, kdb
lets you debug directly on the machine that failed, with or without
compiling with -g. Almost all the differences flow from that design
decision.
Another important niggle to me is that kgdb requires the kernel to be
compiled with frame pointers, because that is all that gdb understands.
On ix86 the extra register pressure from dedicating ebp to frame
pointers can cause Heisenbugs. kdb works with and without frame
pointers.
Can kgdb handle the special hard wired calls that do not add frame
pointers, such as __down_failed? I doubt that gdb knows how to handle
those.
I am not knocking kgdb, it has its place. I see a spectrum of
debugging tools from UML through kgdb to kdb, each tool is aimed at a
different debugging environment. Pick the right tool.
next prev parent reply other threads:[~2002-03-30 3:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-30 2:38 Jeremy Jackson
2002-03-30 3:18 ` Andrew Morton
2002-03-30 3:46 ` Keith Owens [this message]
2002-03-30 4:24 ` Andrew Morton
2002-03-30 4:25 ` David S. Miller
2002-03-30 15:22 ` Peter Wächtler
2002-04-01 9:20 ` Amit S. Kale
2002-04-01 13:44 ` Philip R. Auld
2002-03-30 4:04 ` Keith Owens
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=2178.1017459962@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=akpm@zip.com.au \
--cc=jerj@coplanar.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®