All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Dietsche <olaf.dietsche--list.linux-kernel@exmail.de>
To: HGadi@ecutel.com (Hari Gadi)
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: module (kernel) debugging
Date: Fri, 22 Mar 2002 00:46:07 +0100	[thread overview]
Message-ID: <87663pmqm8.fsf@tigram.bogus.local> (raw)
In-Reply-To: <E16oBVq-0006Z6-00@the-village.bc.nu>

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

>> I am new to kernel level development. What are the best ways to debug runtime
>> kernel (module).
>
> Your brain 8)

I can confirm this :-).

>> Are there any third party tools for debugging the kernel.

A _first_ party tool, which comes to my mind is:
	printk(KERN_DEBUG "whatever\n");
The advantage with printk() is, others can test and debug your module
as well and report results to you.

Regards, Olaf.

  parent reply	other threads:[~2002-03-21 23:57 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 [this message]
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
  -- 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=87663pmqm8.fsf@tigram.bogus.local \
    --to=olaf.dietsche--list.linux-kernel@exmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.