From: Andi Kleen <ak@suse.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: Paul J Albrecht <pjalbrecht@home.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel Debuggers, KDB or KGDB?
Date: Wed, 2 May 2001 16:58:16 +0200 [thread overview]
Message-ID: <20010502165816.A8450@gruyere.muc.suse.de> (raw)
In-Reply-To: <01043016264000.00697@CB57534-A> <18223.988679810@kao2.melbourne.sgi.com>
In-Reply-To: <18223.988679810@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Tue, May 01, 2001 at 11:16:50AM +1000
On Tue, May 01, 2001 at 11:16:50AM +1000, Keith Owens wrote:
> 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.
http://pice.sourceforge.net is one approach to it; but it's currently
a bit limited: e.g. ATM UP-i386-2.2 only and somewhat windowish; also the
approach only really works for modules not complete kernel sources unless
you have a *lot* of memory. Still in its limits it works.
-Andi
next prev parent reply other threads:[~2001-05-02 14:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 21:17 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
2001-05-02 14:58 ` Andi Kleen [this message]
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=20010502165816.A8450@gruyere.muc.suse.de \
--to=ak@suse.de \
--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
all inboxes | Powered by JetHome®