From owner-freebsd-hackers  Sat Jun 21 01:38:12 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA19372
          for hackers-outgoing; Sat, 21 Jun 1997 01:38:12 -0700 (PDT)
Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA19306
          for <hackers@FreeBSD.ORG>; Sat, 21 Jun 1997 01:35:56 -0700 (PDT)
Received: (babkin@localhost) by hq.icb.chel.su (8.8.3/8.6.5) id OAA01256; Sat, 21 Jun 1997 14:38:26 +0600 (ESD)
From: "Serge A. Babkin" <babkin@hq.icb.chel.su>
Message-Id: <199706210838.OAA01256@hq.icb.chel.su>
Subject: Re: debugging kernel's code
To: igor@blik.samara.su (Igor)
Date: Sat, 21 Jun 1997 14:38:25 +0600 (ESD)
Cc: hackers@FreeBSD.ORG
In-Reply-To: <AAsKKgpa33@blik.samara.su> from "Igor" at Jun 19, 97 07:41:58 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> what are the methods of debugging kernel's code ?

There exists the DDB kernel debugger. I use it primarily for analysing
the panics. There exisgs KGDB (Kernel GDB) too but I never tried to use
it. And of course the classic method of adding printf()s is all
the time with us!

-SB