public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, HGadi@ecutel.com
Subject: Re: module (kernel) debugging
Date: 22 Mar 2002 02:26:56 +0100	[thread overview]
Message-ID: <p73zo111jfj.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <AF2378CBE7016247BC0FD5261F1EEB210B6A93@EXCHANGE01.domain.ecutel.com.suse.lists.linux.kernel> <E16oBVq-0006Z6-00@the-village.bc.nu.suse.lists.linux.kernel>

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

> 
> 	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)
        pice    -       Private Ice. Source level debugger for modules, 
                        doesn't need a kernel patch and works with a single
                        machine. 2.2/UP only at the 
                        moment, but can be ported to 2.4. Loosely similar to 
                        Softice on Windows.

-Andi

       reply	other threads:[~2002-03-22  1:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2002-03-25  6:48 module (kernel) debugging Rick A. Hohensee
  -- strict thread matches above, loose matches on Subject: below --
2002-03-21 22:15 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

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=p73zo111jfj.fsf@oldwotan.suse.de \
    --to=ak@suse.de \
    --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