public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@karaya.com>
To: LA Walsh <law@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: To Linus: kdb in 2.4?
Date: Tue, 13 Feb 2001 19:07:59 -0500	[thread overview]
Message-ID: <200102140007.TAA04135@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Tue, 13 Feb 2001 13:53:52 PST." <3A89ACF0.142CB71B@sgi.com>

law@sgi.com said:
> I'm wondering about the possibility of re-examining the idea of a
> kernel debugger option distributed with 2.4.   

First off, I'd like to say that I'm highly sympathetic to this, assuming that 
a kernel debugger doesn't change the kernel's behavior.

However, 

> I'm thinking that it could be a great teaching tool to break and
> examine structures, variables, process states, as well as an aid to
> people who may not have a grasp of the entire kernel but need to write
> device drivers. 

you might look at UML (http://user-mode-linux.sourceforge.net) for this.  A 
number of kernel hackers are very successfully using UML for doing filesystem 
and mm development and debugging.  With some help from the host, it's also 
possible to do driver development under UML.

I also know of a number of people using UML to further their education by 
using it to poke around a running kernel.

> Certainly Buddha doesn't need to know how to read to know his own
> writings -- and certainly, if everyone meditates and 'evolves' to
> their Buddha nature, they wouldn't need to read the texts or recognize
> the letters either.   

So, if you can't convince Buddha of the wisdom of your arguments (or even if 
you can) check out UML.  It makes a perfectly good kernel debugger available, 
and it's a lot easier to deal with than a native kernel.

				Jeff



  reply	other threads:[~2001-02-13 22:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-13 21:53 To Linus: kdb in 2.4? LA Walsh
2001-02-14  0:07 ` Jeff Dike [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-13 23:14 Hacksaw

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=200102140007.TAA04135@ccure.karaya.com \
    --to=jdike@karaya.com \
    --cc=law@sgi.com \
    --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