public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: "Amit S. Kale" <akale@veritas.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	Hari Gadi <HGadi@ecutel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: module (kernel) debugging
Date: Thu, 21 Mar 2002 22:54:41 -0800	[thread overview]
Message-ID: <3C9AD531.C2C8C178@zip.com.au> (raw)
In-Reply-To: <AF2378CBE7016247BC0FD5261F1EEB210B6A93@EXCHANGE01.domain.ecutel.com> <20020322000823.GD785@holomorphy.com> <3C9AD0EB.C56CE9B7@veritas.com>

"Amit S. Kale" wrote:
> 
> William Lee Irwin III wrote:
> >
> > On Thu, Mar 21, 2002 at 05:15:48PM -0500, Hari Gadi wrote:
> > > Hi,
> > > I am new to kernel level development. What are the best ways to debug
> > > runtime kernel (module). Are there any third party tools for debugging
> > > the kernel.
> >
> > http://www.arium.com
> > http://oss.sgi.com/projects/kdb
> > http://oss.sgi.com/projects/kgdb
> 
> SGI's kgdb is for 2.2 kernels only.
> kgdb for 2.4 kernels resides at http://kgdb.sourceforge.net/
> You'll find there scripts for debugging modules with kgdb.
> 

I have 2.5 kgdb stub patches too.  Various versions can be discovered
by poking around in http://www.zip.com.au/~akpm/linux/patches/

The version I use is a bit thinner than Amit's - I took out the
assertion checks from various places because they cause patching pain.
The assertion mechanism is still there, but the *uses* of it I took
out.

Of course, I may not be feature- or bugfix-current against Amit's
version.

-

  reply	other threads:[~2002-03-22  6:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-21 22:15 module (kernel) debugging Hari Gadi
2002-03-21 22:58 ` Alan Cox
2002-03-21 23:30   ` Jeff V. Merkey
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 [this message]
     [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
  -- strict thread matches above, loose matches on Subject: below --
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=3C9AD531.C2C8C178@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=HGadi@ecutel.com \
    --cc=akale@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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