From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Hari Gadi <HGadi@ecutel.com>, linux-kernel@vger.kernel.org
Subject: Re: module (kernel) debugging
Date: Thu, 21 Mar 2002 16:30:15 -0700 [thread overview]
Message-ID: <20020321163015.A25688@vger.timpanogas.org> (raw)
In-Reply-To: <AF2378CBE7016247BC0FD5261F1EEB210B6A93@EXCHANGE01.domain.ecutel.com> <E16oBVq-0006Z6-00@the-village.bc.nu>
One more:
MDB - source level kernel debugger.
:-)
Jeff
On Thu, Mar 21, 2002 at 10:58:26PM +0000, Alan Cox wrote:
> > I am new to kernel level development. What are the best ways to debug runtime
> > kernel (module).
>
> Your brain 8)
>
> > Are there any third party tools for debugging the kernel.
>
> Several
>
> kgdb - debug the kernel with gdb from another PC
> kdb - patch for in kernel debugger
> UML - user mode linux (good for fs not so good for driver
> work)
> -
> 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/
next prev parent reply other threads:[~2002-03-21 23:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 22:15 Hari Gadi
2002-03-21 22:58 ` Alan Cox
2002-03-21 23:30 ` Jeff V. Merkey [this message]
2002-03-21 23:29 ` Christoph Hellwig
2002-03-22 0:33 ` Jeff V. Merkey
2002-03-22 0:33 ` Jeff V. Merkey
2002-03-22 0:40 ` Jeff V. Merkey
2002-03-21 23:46 ` Olaf Dietsche
2002-03-22 0:08 ` William Lee Irwin III
2002-03-22 6:36 ` Amit S. Kale
2002-03-22 6:54 ` Andrew Morton
[not found] <AF2378CBE7016247BC0FD5261F1EEB210B6A93@EXCHANGE01.domain.ecutel.com.suse.lists.linux.kernel>
[not found] ` <E16oBVq-0006Z6-00@the-village.bc.nu.suse.lists.linux.kernel>
2002-03-22 1:26 ` Andi Kleen
2002-03-25 6:48 Rick A. Hohensee
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=20020321163015.A25688@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=HGadi@ecutel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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®